os-backlog: record planka-api 0.2.0 migration in docs (implementation-status timeline + stale 0.1.0 mentions) #19
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#19
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What to build
Commit
8df0cb7(planka-api 0.2.0 typed-returns migration) shipped without the required record-keeping. Per repo convention, add a timeline entry to docs/implementation-status.md describing the migration (typed Planka::Types accessors, BoardDetail replacing the included-hash, rebuilt test fakes) and update the os-backlog component section, which still says planka-api gem 0.1.0 is installed locally. Keep dates absolute (2026-07-10). Reference the snapshot-field regression fix (#18) once landed so the record describes the corrected state. No design change occurred, so CLAUDE.md's design paragraph stays untouched.Acceptance criteria
Blocked by