docs: drop area/web Fable routing rule

The rule justified pinning area/web issues to Fable 5 by saying they go through the impeccable skill. That skill is symlinked into codex as well, so it says nothing about which model to use. area/web now routes by difficulty label like every other area; line 47 already requires impeccable for anything that decides how something looks. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-24 16:55:23 +01:00
parent 869e3af9c8
commit d5fc790839
1 changed files with 0 additions and 4 deletions
@@ -223,10 +223,6 @@ bogus ID as a control to prove the check discriminates:
 accepted. The bogus control (`gpt-5.6-nonesuch`) failed with HTTP 400, and
 `claude-bogus-9` was rejected by the CLI.
 **`area/web` issues run on Fable 5 regardless of their difficulty label**, since
 they go through the `impeccable` skill and the UI is the reason this project
 has a frontend at all (see the design section above).
 Escalate one tier if a session fails CI twice on the same issue — and escalate
 to the *other* model at that tier first, before going up. Never de-escalate
 mid-issue.