[jussi-modernpath]

Upstream half of Epic 298 "Keep backlog routing truthful" (ModernPath, TEST-ModernPath-v1), requirement SR-3815: the skills say how a backlog, gap or tooling record that an Epic plan delivers is routed and closed, PROCESS.md says the records are created, routed and closed on the server, and §Small changes says what happens to a record a small change delivers. The monorepo re-pins the kit after this merges.

The second commit (2483064) answers the maintainer's feedback that the first wording was hard to read: it uses the kit's own term, "the CLI" (adopted in 1cbe01a), instead of "the sanctioned process interface", splits each step into one instruction per sentence, and adds the small-change paragraph.

Added text

skills/rdd-plan/SKILL.md (step 7, after the plan save and read-back):

Then use the CLI to mark each backlog, gap or tooling record the plan delivers as routed to the Epic, with a reference to this plan save, and read the record back. List those records in the plan body. Do the same when a later plan save adds a record.

skills/rdd-triage/SKILL.md (step 3, where a discovery changes a plan):

When a saved plan delivers a backlog, gap or tooling record, use the CLI to mark the record as routed to that Epic, with a reference to the plan save, and read it back. Listing the record in the plan body does not route it.

skills/rdd-completion-review/SKILL.md (new step 6, after the publication read-back):

After that publication is read back, use the CLI to mark each backlog, gap or tooling record routed to the Epic as closed by the Epic, and read each record back. If the human wants a record left open, leave it open and add a note saying why.

skills/rdd-deliver/SKILL.md (step 6, the completion step): the same text, opening with "After completion approval is read back".

PROCESS.md §Discoveries and conflicts (after the route table; restores the statement removed in #48):

Backlog, gap and tooling records live on the server like every other delivery record: they are created, routed and closed there, through the CLI. When a saved plan delivers a record, mark the record as routed to that Epic. After human completion approval, mark it as closed by that Epic. If the human wants a record left open, leave it open and add a note saying why. Whether a record is open, routed or closed (its disposition) is read from the server, not from the plan text; a plan only lists the records it delivers. A discovery that exists only in a note is not yet a record.

PROCESS.md §Small changes (end of the section):

A small change has no Epic to route a backlog, gap or tooling record to. When it delivers such a record, name the record in the PR. If the change cites a requirement, use the CLI to mark the record as routed to that requirement and read it back. Once the change merges, use the CLI to mark the record as closed by that pull request and read it back.

No command, flag or field is named; the project's CLI reference maps "routed to" and "closed by" to its command. The small-change paragraph matches what the server accepts: a routing target must be an Epic or a requirement of the System, and a closing source may be a pull request.

PR #52

PR #52 (Epic 291) is closed, so the earlier overlap note no longer applies. This branch is rebased onto main at 4bca3db.

Checks (at 2483064)

• git diff --check 4859893..2483064: clean; prek run --from-ref 4859893 --to-ref 2483064 (the repo's whitespace check): passed
• git grep -i backlog: two paragraphs in PROCESS.md and one sentence group in each of the four skills; no other kit file mentions it
• no "sanctioned", "projection" or "disposition to routed" left anywhere in the kit
• no (RUN|USER):YYYY-MM-DD stamp in any skill (the shipped-skill test in the monorepo rejects them)

🤖 Generated with Claude Code