workflow: replace docs/roadmap.md with Gitea issue backlog

The forward queue moves out of the in-tree markdown file and into
Gitea issues at http://192.168.178.103:3000/Brummel/AILang/issues.
Labels: kind:{milestone,feature,todo,idea} + prio:{p1,p2,p3}
+ state:in-progress. Big chunks live as Gitea milestones
(containers) with full prose in the description; smaller items are
standalone issues. Browse-and-filter scales constant against
growing item count; the previous markdown file was 1059 lines, of
which ~850 were already-closed-entry verlauf (the same failure
class the JOURNAL cut removed).

Sync-drift Code<>Tracker mitigation: Soft-convention `closes #N`
/ `refs #N` in commit bodies — Gitea auto-closes the issue on
push. Captured in user-level CLAUDE.md (~/.claude/CLAUDE.md, not
in this commit) as the durable rule; no hook enforcement.

In-repo changes:

- docs/roadmap.md deleted.
- CLAUDE.md (project): Code-layout drops roadmap; /boss gating
  retargeted; Roles section rewritten with a new "Gitea issues"
  bullet (URL + tea-CLI snippet) and the closes-#N trailer note.
- skills/boss/SKILL.md: 10 sites retargeted, plus Step 1 now
  prescribes `tea issues ls --labels prio:p1` as the queue read.
- skills/brainstorm/SKILL.md: Step 7.5 no-override BLOCK now
  files a Gitea issue via `tea issues create` instead of
  appending a roadmap entry; spec deletion stays.
- skills/audit/SKILL.md + ailang-architect.md: deferral
  requirement and debt-heuristic retargeted; forward-intent
  belongs in the Gitea backlog.
- skills/fieldtest/SKILL.md, skills/docwriter/SKILL.md +
  ailang-docwriter.md: roadmap → backlog.
- design/contracts/honesty-rule.md: forward intent lives in
  the Gitea backlog (pinned phrases unchanged).
- design/INDEX.md: Docs bullet drops roadmap, adds the backlog
  URL.
- crates/ailang-core/tests/docs_honesty_pin.rs: two assert
  messages retargeted (assertion bodies unchanged).
- bench/architect_sweeps.sh: Sweep-4 TABU extended with
  `docs/roadmap\.md` so the deleted path cannot quietly regrow
  as a cross-reference in design/contracts/.

Verification:

- cargo build --workspace clean.
- cargo test --workspace: 647 passed, 0 failed, 2 ignored.
- bench/architect_sweeps.sh exit 0 (all five sweeps clean, incl.
  new TABU).
- grep over the live tree (excluding docs/specs/, docs/plans/)
  shows zero residual docs/roadmap.md refs.

Not touched: ~55 historical files under docs/specs/ and
docs/plans/ that mention docs/roadmap.md. Snapshot-character,
analogous to the JOURNAL-cut precedent — historical specs are
not mass-edited just because a live file was retired; their
mentions were correct at write time.

skills/brainstorm/SKILL.md

@@ -242,19 +242,22 @@ interpretation:
 1. Delete the just-written spec file from the working tree
    (`rm docs/specs/<spec_filename>.md` — a Bash-level delete on the
    working tree, NOT `git rm`; the file was never committed).
-2. Append a roadmap entry to `docs/roadmap.md` pointing forward to a
-   future re-brainstorm, under the appropriate priority bucket:
+2. Open a Gitea backlog issue pointing forward to a future
+   re-brainstorm, under the appropriate priority bucket:
 
-   ```markdown
-   - [ ] **[<kind>]** <idea title> — <one-line description>
-     - context: <why this is deferred>
-     - depends on: <name of the unratified mechanism>
+   ```bash
+   tea issues create --repo Brummel/AILang \
+     --title "<idea title>" \
+     --labels "kind:<milestone|feature|todo|idea>,prio:p2" \
+     --description "<one-line description>
+
+   **context:** <why this is deferred>
+   **depends on:** <name of the unratified mechanism>"
    ```
 
-3. Tell the user the spec was retired and which roadmap entry was
-   added. The user / Boss commits the roadmap edit (suggested
-   commit subject: `spec: retire <spec topic> — depends on
-   <unratified mechanism>`).
+3. Tell the user the spec was retired and which Gitea issue was
+   filed (include the issue number). No commit is needed for the
+   backlog entry — Gitea is the live store.
 
 After the failure-mode procedure runs, the brainstorm session ENDS.
 There is no Step 8, no Step 9. The idea is parked until the
@@ -305,7 +308,7 @@ Hand off carries:
 | user → `brainstorm` | new milestone request |
 | `brainstorm` → `ailang-grounding-check` (Step 7.5) | `spec_path` + `iteration_scope` |
 | `brainstorm` → `planner` (Step 9, on PASS or overridden BLOCK) | path to spec + iteration scope |
-| `brainstorm` → roadmap (Step 7.5, on no-override BLOCK) | `depends on:` entry added to `docs/roadmap.md` in the working tree, spec file deleted from the working tree; Boss commits the roadmap edit |
+| `brainstorm` → Gitea backlog (Step 7.5, on no-override BLOCK) | new issue opened via `tea issues create` naming the unratified dependency; spec file deleted from the working tree (no commit needed) |
 
 ## Common Rationalisations