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/docwriter/SKILL.md

@@ -26,7 +26,7 @@ Trigger conditions are any of:
 
 - `cargo doc --no-deps 2>&1` shows accumulated warnings across
   multiple crates after a stability window of several milestones.
-- A roadmap entry like "Rustdoc warning sweep" has matured — the
+- A backlog issue like "Rustdoc warning sweep" has matured — the
   surface it targets has not moved for a while.
 - Onboarding-readability check: navigating `cargo doc --open` for a
   crate is not self-supporting without the design/ ledger.
@@ -86,4 +86,4 @@ iteration; `docwriter` does not self-resolve.
   Fieldtest can surface bugs or architecture problems that would
   invalidate the doc work.
 - **Hand-off target:** orchestrator (me). Findings flow into the
-  roadmap as candidates for a follow-up tidy iteration.
+  Gitea backlog as candidates for a follow-up tidy iteration.

skills/docwriter/agents/ailang-docwriter.md

@@ -89,7 +89,7 @@ YOU NEVER COMMIT. RUSTDOC EDITS LIVE IN THE WORKING TREE; THE BOSS COMMITS.
   confusing it needs renaming, raise it in your report instead of changing
   it.
 - No new `pub` exports. Visibility stays as-is.
-- No edits in `docs/` or `design/`. The orchestrator owns the design/ ledger and the roadmap.
+- No edits in `docs/` or `design/`. The orchestrator owns the design/ ledger and the Gitea backlog.
 - Don't paper over broken behaviour with prose — if doc-writing surfaces
   a real bug (a function whose doc you cannot honestly write because it
   doesn't actually do what it claims), stop and report it.