docs(framework): describe the board we actually run

[blafourcade]

🎯 What & why

The maintainer docs describe a board that no longer exists. Every row below was checked against the live project #8 and the repo today.

The doc said	Reality
Set Status / Area / Priority	Area is deleted; the scope lives in the issue title
Type = the label	Type is an issue type, stamped by the form (#422)
Keep Priority (P0 · P1 · P2)	Options are Urgent · High · Medium · Low, and it is an org issue field, not a board field
Status: Todo · In progress · In review · Ready · Done	Ideation · Todo · In Progress · In review · Done. No Ready
Drop Work type and Phases	Neither field exists
Timeline view, date = Milestone/target	The roadmap layout cannot read a milestone as a date
"The sync loop creates/updates from the file"	No workflow syncs labels. There never was one
ROADMAP.md: Now / Next / Later, framework and CLI	No such field; aidd-cli was removed from the board

🛠️ How it works

docs/MAINTAINERS.md — the board section becomes four orthogonal axes, one table, plus the two rules that keep them orthogonal: a milestone or a priority, never both, and the scope lives in the title. The labels section states what a label is for now that types categorize.

aidd_docs/memory/vcs.md — the routing table's Label (auto) column becomes Issue type. The board-advance line drops the Ready step that does not exist.

ROADMAP.md — one sentence, describing the board as it is.

.github/workflows/back-merge.yml — drops --label "back-merge-failed". This is a live bug, not a doc fix. The label never existed, so gh issue create failed; the trailing || echo "issue creation failed" swallowed the error and the step stayed green. A failed back-merge therefore opened no issue and raised no alarm — exactly what the comment two lines above forbids:

# Never let a back-merge fail silently: a rejected push or any other error opens a tracking issue

Nothing read the label: git grep back-merge-failed matched the workflow and the doc sentence describing it, nothing else.

🧪 How to verify

yq e '.' .github/workflows/back-merge.yml >/dev/null && echo "workflow parses"
git grep -c back-merge-failed ; echo "exit=$?  # 1 = gone"

# no stale reference to the dead model survives outside the changelog and archived plans
git grep -nE '\bP0\b|`Area`|Now / Next / Later|`Ready`|`enhancement`' \
  -- ':!CHANGELOG.md' ':!aidd_docs/plans' ':!aidd_docs/specs' ':!aidd_docs/tasks'

The live board: gh project field-list 8 --owner ai-driven-dev returns exactly one single-select, Status.

✅ I certify

• I DO CERTIFY I READ EACH LINE OF THE PULL REQUEST BECAUSE I AM A SOFTWARE ENGINEER, NOT A AI PUPPY.