coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Review stale TODO.md — activity-core #4

New issue
Closed
opened 2026-07-08 13:35:26 +00:00 by tegwick · 1 comment
tegwick commented 2026-07-08 13:35:26 +00:00
Owner
Copy link

TODO.md unchanged for 18 days (mtime 2026-06-20T12:00:00+00:00). Review open items: archive done work, delete noise, or promote valuable topics to a workplan file and run statehub fix-consistency.

TODO.md unchanged for 18 days (mtime 2026-06-20T12:00:00+00:00). Review open items: archive done work, delete noise, or promote valuable topics to a workplan file and run statehub fix-consistency.
tegwick commented 2026-07-20 21:49:44 +00:00
Author
Owner
Copy link

Reviewed 2026-07-20. activity-core no longer has a TODO.md at all (git history confirms it was never a tracked file in this repo — ephemeral/untracked when the daily-todo-md-stale-review scan ran, since removed). The repo plans entirely via ADR-001 workplans/ (currently ACTIVITY-WP-0019, WP-0020, etc. — an active, well-maintained backlog). The flag is moot; nothing to archive or promote. Closing.

Separate finding surfaced while reviewing this: the ActivityDefinition that created this issue (the-custodian/activity-definitions/daily-todo-md-stale-review.md, enabled: true, daily 08:30) routes through activity-core's default "rest" issue-sink -> issue-core -> Forgejo, which is how issues #1-5 came to exist. Per current policy (Forgejo issue tracking is not the fleet coordination mechanism), this routing is being redirected onto the work-record backbone (CUST-WP-0060) rather than Forgejo issues — follow-up tracked separately.

Reviewed 2026-07-20. activity-core no longer has a TODO.md at all (git history confirms it was never a tracked file in this repo — ephemeral/untracked when the daily-todo-md-stale-review scan ran, since removed). The repo plans entirely via ADR-001 workplans/ (currently ACTIVITY-WP-0019, WP-0020, etc. — an active, well-maintained backlog). The flag is moot; nothing to archive or promote. Closing. Separate finding surfaced while reviewing this: the ActivityDefinition that created this issue (the-custodian/activity-definitions/daily-todo-md-stale-review.md, enabled: true, daily 08:30) routes through activity-core's default "rest" issue-sink -> issue-core -> Forgejo, which is how issues #1-5 came to exist. Per current policy (Forgejo issue tracking is not the fleet coordination mechanism), this routing is being redirected onto the work-record backbone (CUST-WP-0060) rather than Forgejo issues — follow-up tracked separately.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: coulomb/the-custodian#4
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?