generated from coulomb/repo-seed
feat(tasks): adopt canonical task statuses
This commit is contained in:
93
docs/task-state-attached-repo-impact.md
Normal file
93
docs/task-state-attached-repo-impact.md
Normal file
@@ -0,0 +1,93 @@
|
||||
# Task State Attached Repo Impact
|
||||
|
||||
Date: 2026-05-25
|
||||
Interface change: `649102a2-4373-4621-9848-cc257e67c262`
|
||||
Status: published
|
||||
|
||||
## Notice Channel
|
||||
|
||||
State Hub published a breaking schema interface change from `state-hub` to all
|
||||
active attached repos except `state-hub` itself.
|
||||
|
||||
The notice points target repos to `docs/task-state-canon-migration.md` and asks
|
||||
their local agents to update any State Hub task-status references:
|
||||
|
||||
```text
|
||||
blocked -> wait
|
||||
in_progress -> progress
|
||||
cancelled/canceled -> cancel
|
||||
todo -> todo
|
||||
done -> done
|
||||
```
|
||||
|
||||
Workstream/workplan lifecycle status is unchanged and still includes
|
||||
`blocked`.
|
||||
|
||||
## Classification
|
||||
|
||||
Classification was based on `GET /repos/` plus a read-only local scan of active
|
||||
repo paths. `legacy-literals` means a repo contains old words such as
|
||||
`blocked`, `in_progress`, `cancelled`, `blocked_tasks`, or `TaskStatus`; the
|
||||
hit can be task state, workstream state, capability/debt status, or prose, so
|
||||
the owning repo agent must review context before editing.
|
||||
|
||||
| Repo | Local path | Classification |
|
||||
|------|------------|----------------|
|
||||
| activity-core | yes | file-backed; legacy-literals |
|
||||
| artifact-store | yes | file-backed; legacy-literals |
|
||||
| can-you-assist | yes | file-backed; legacy-literals |
|
||||
| citation-engine | yes | general notice only |
|
||||
| citation-evidence | yes | file-backed |
|
||||
| citation-work | yes | general notice only |
|
||||
| domain-tree | yes | file-backed; legacy-literals |
|
||||
| evidence-anchor | yes | general notice only |
|
||||
| evidence-binder | yes | general notice only |
|
||||
| evidence-source | yes | general notice only |
|
||||
| flex-auth | yes | file-backed; legacy-literals |
|
||||
| guide-board | yes | file-backed; legacy-literals |
|
||||
| helix-forge | yes | file-backed; legacy-literals |
|
||||
| ihp-railiance-probe | yes | file-backed; legacy-literals |
|
||||
| info-tech-canon | yes | canon source; file-backed |
|
||||
| infospace-bench | yes | file-backed; legacy-literals |
|
||||
| inter-hub | yes | file-backed; legacy-literals |
|
||||
| issue-core | yes | file-backed; likely State Hub/task lifecycle client; legacy-literals |
|
||||
| kaizen-agentic | no | general notice only |
|
||||
| key-cape | yes | file-backed; legacy-literals |
|
||||
| kontextual-engine | yes | file-backed; legacy-literals |
|
||||
| llm-connect | yes | file-backed; legacy-literals |
|
||||
| marki-docx | no | general notice only |
|
||||
| markitect-filter | yes | file-backed; legacy-literals |
|
||||
| markitect-project | yes | file-backed; legacy-literals |
|
||||
| markitect-quarkdown | yes | file-backed; legacy-literals |
|
||||
| markitect-tool | yes | file-backed; legacy-literals |
|
||||
| net-kingdom | yes | file-backed; legacy-literals |
|
||||
| open-cmis-tck | yes | file-backed; legacy-literals |
|
||||
| open-reuse | yes | file-backed; legacy-literals |
|
||||
| ops-bridge | yes | file-backed; legacy-literals |
|
||||
| ops-warden | yes | file-backed; legacy-literals |
|
||||
| phase-memory | yes | file-backed; legacy-literals |
|
||||
| railiance-apps | yes | file-backed; legacy-literals |
|
||||
| railiance-cluster | yes | file-backed; legacy-literals |
|
||||
| railiance-enablement | yes | file-backed; legacy-literals |
|
||||
| railiance-fabric | yes | file-backed; legacy-literals |
|
||||
| railiance-hosts | yes | file-backed; legacy-literals |
|
||||
| railiance-infra | yes | file-backed; legacy-literals |
|
||||
| railiance-platform | yes | file-backed; legacy-literals |
|
||||
| repo-scoping | yes | file-backed; legacy-literals |
|
||||
| the-custodian | yes | file-backed; likely State Hub/task lifecycle client; legacy-literals |
|
||||
| user-engine | yes | file-backed |
|
||||
| vergabe-teilnahme | yes | file-backed; legacy-literals |
|
||||
| vergabe_teilnahme | yes | file-backed; legacy-literals |
|
||||
|
||||
## Requested Repo-Agent Action
|
||||
|
||||
Each repo agent should:
|
||||
|
||||
1. Read its State Hub inbox notice for interface change
|
||||
`649102a2-4373-4621-9848-cc257e67c262`.
|
||||
2. Search local agent instructions, workplans, scripts, docs, tests,
|
||||
dashboards, and API clients for State Hub task-status values.
|
||||
3. Replace task-state usage with canonical values and leave unrelated
|
||||
workstream/capability/debt statuses unchanged.
|
||||
4. Report completion by replying in State Hub or resolving the interface change
|
||||
for that repo once local adaptation is complete.
|
||||
Reference in New Issue
Block a user