fix(workplans): declare records the hub already holds as workplans
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

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
This commit is contained in:
codex 2026-08-26 10:29:35 +02:00
parent ea29566025
commit 2ba22ebbbc

View file

@ -1,9 +1,13 @@
---
type: session-note
id: ACTIVITY-WP-0037
type: workplan
created: "2026-03-28"
updated: "2026-06-03"
status: archived
state_hub_workstream_id: "b221e65a-6f97-44b0-8dae-442fffcb7f64"
title: "Session notes and next steps"
domain: infotech
repo: activity-core
---
> **Terminology note:** Historical text in this archived workplan may use the legacy term "workstream". The fleet term is **workplan** (`canon/standards/workplan-terminology-fleet_v0.1.md`).