docs(backlog): serve COR-104-T10 before COR-102, and make the tracking files true #442

Problem

just next serves COR-102-T1 (Canadian French) first. COR-104-T10 waits behind three French cards, but COR-104-T10 is the only card that tests the verification loop on a real extension. Some plan files are also out of date:

• docs/status.md did not change after 2026-10-29. It does not mention just finish or COR-104.
• The COR-104-T1 card says 154 rules and 11 "Prose on purpose". At 318978e, just status counts 169 and 13.
• The milestone COR-102 Canadian French holds 0 issues, and no milestone exists for COR-104.
• The parity test of COR-102-T1 does not find English text that is hard-coded outside the catalogs. Examples: sdk/extensionrepo/update.go lines 47, 51, 79, and 80, signoff.go line 140, release_install.go lines 50, 87, and 94, and internal/cli/values.go lines 98-152.
• COR-625 (AUR package) is an idea, but Pascal chose it on 2026-11-03. A chosen idea gets the next free 1xx ID.

Goal

The queue serves the work that tests the loop first, and the plan files give current facts.

Pascal decided this order on 2026-11-03: COR-104-T10 first, then COR-102, then one real everyday extension. He also chose the AUR package.

Acceptance rules

This is a plan-only pull request. It changes no code.

1. The queue in docs/backlog/README.md is 1. COR-104, 2. COR-102, 3. COR-105.
2. The pull request moves the milestones as the Plan rules of docs/backlog/README.md say:
   • It creates the milestone COR-104 verification map, with the description First item of the backlog queue: docs/backlog/COR-104-verification-map.md, and puts template: an existing extension adopts just finish after the update #427 in it.
   • The milestone COR-102 Canadian French stays open, with its description.
3. COR-102-T1 starts with a check that finds user-visible English strings outside the catalogs, in core and in sdk/. The card names the files above as its first known cases.
4. Under After in COR-104, a new step compares the time and findings of each gate in template: an existing extension adopts just finish after the update #427. The step then removes each gate that took time and found no real defect. Pascal accepts each removal.
5. The state of XT-602 gives its revisit condition: after COR-102 ships, deliver one small useful slice through the loop.
6. COR-625 becomes docs/backlog/COR-105-aur-package.md, as "Make an item ready" in docs/backlog/README.md says. Its frontmatter is id: COR-105, core: "AUR package", state: "Ready. T1 waits on Pascal". Its Demo is one sentence: "yay -S ncly-bin on Omarchy installs the released ncly." Its card table has two rows:
   • COR-105-T1 AUR account and release key, owner Pascal, depends on nothing, todo (chore(release): Pascal opens the AUR account for ncly-bin #448)
   • COR-105-T2 Publish ncly-bin with each release, owner agent, depends on COR-105-T1, todo (feat(release): each release publishes ncly-bin to the AUR #449). Its section has Read: the release-nicely skill and .goreleaser.yaml, and Proves: .goreleaser.yaml.
7. docs/status.md describes just finish, COR-104, and the queue at the merge commit.
8. The COR-104-T1 card gives the counts that just status prints at the merge commit.
9. The pull request fixes stale item and card references in each open 4-epic issue, and lists them, as docs/backlog/README.md says.

Examples

• Success: on the merge commit, just next prints COR-104-T10.
• Failure: just next prints COR-102-T1.

Check

• just next prints COR-104-T10.
• just check passes.
• gh issue view 427 -R pascalandy/nicely --json milestone names the milestone of COR-104.

by Opus-5.5 via Claude Code