railiance-bootstrap/workplans
codex 9c0b3a2b0f
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
fix(workplans): declare records the hub already holds as workplans
Canon defines six work-record kinds — workplan, task, intake, decision,
engagement, register-entry. These files declared none of them (feature, runbook,
bug-report, extension-workplan, scorecard, session-note, adhoc) while the hub
held each as a workplan.

Selection is by 'type: workplan', so the mismatch made them invisible to any
projection: a forge-derived reset read their correct hub records as no longer
deriving and proposed retiring live work.

Where a file also lacked a canonical identifier, one was assigned continuing the
repository's sequence. Existing hub identifiers are preserved, so no record is
orphaned.

Refs STATE-WP-0083

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
2026-08-26 10:29:32 +02:00
..
archived fix(workplans): declare records the hub already holds as workplans 2026-08-26 10:29:32 +02:00
RAIL-BS-WP-0008-activity-core-wp0016-triage-output-deploy.md RAIL-BS-WP-0008/0009 finished: live deploy, top-7 proof, admin-sync smoke 2026-07-02 11:53:11 +02:00
RAIL-BS-WP-0009-activity-core-admin-sync-smoke.md RAIL-BS-WP-0008/0009 finished: live deploy, top-7 proof, admin-sync smoke 2026-07-02 11:53:11 +02:00