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

@@ -1,6 +1,6 @@
 ---
 name: audit
-description: Use at milestone close OR when baseline drift is suspected. Runs architect drift review against the design/ ledger (spine design/INDEX.md) plus the three regression scripts (bench/check.py, bench/compile_check.py, bench/cross_lang.py). Mandatory at every milestone close; deferral requires an explicit roadmap entry naming the reason and the re-run date.
+description: Use at milestone close OR when baseline drift is suspected. Runs architect drift review against the design/ ledger (spine design/INDEX.md) plus the three regression scripts (bench/check.py, bench/compile_check.py, bench/cross_lang.py). Mandatory at every milestone close; deferral requires an explicit Gitea backlog issue naming the reason and the re-run date.
 ---
 
 # audit — milestone-tidy
@@ -17,7 +17,7 @@ iteration of a milestone closes and before the next milestone starts.
 ## When to Use / Skipping
 
 **Mandatory** at every milestone close. Skipping requires an explicit
-roadmap entry naming:
+Gitea backlog issue naming:
 - the blocking sibling milestone (if any),
 - the reason for deferral,
 - the date the audit will be re-run.
@@ -129,7 +129,7 @@ self-resolve.
 - Bumping baseline without a paired ratify statement in the audit commit body
 - Treating exit code 2 as a regression to fix
 - Closing a milestone with drift items in `pending` state
-- "We'll re-run after the holidays" without a dated roadmap entry
+- "We'll re-run after the holidays" without a dated backlog issue
 
 ## Cross-references
 

skills/audit/agents/ailang-architect.md

@@ -62,7 +62,7 @@ If `milestone_scope` is empty, return a structural error and stop.
 - **Drift against the milestone spec** (if one exists). Does the code match
   the spec's *Components* and *Data flow* sections?
 - **Growing debt.** Heuristics where the schema is authoritative,
-  TODO/FIXME without a roadmap entry or named owner, `#[allow(dead_code)]`
+  TODO/FIXME without a backlog issue or named owner, `#[allow(dead_code)]`
   spots that will tip over long-term, magic numbers without named
   constants in hot paths.
 - **Consistency across crates.** AST changes that landed in one crate but
@@ -93,8 +93,9 @@ If `milestone_scope` is empty, return a structural error and stop.
   `design/contracts/honesty-rule.md`: a hit is
   drift unless it is a present-tense correctly-labelled
   reserved/excluded claim, present-tense design rationale, or a
-  block-quote commit-body citation. Forward intent is roadmap drift;
-  document/project history belongs in `git log`, not in `design/`.
+  block-quote commit-body citation. Forward intent belongs in the
+  Gitea backlog; document/project history belongs in `git log`, not
+  in `design/`.
 - **Lockstep invariants across files.** Two known cross-file pairings
   must move together; a new arm in one without the matching update in
   the other ships silently broken (B1 in the Floats fieldtest is the