coulomb/activity-core
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
activity-core/workplans/ADHOC-2026-08-20.md
repo-manager ab10835a0c
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
repo.work.assign_missing_identifiers 
source: repo-manager
reason: deterministic projection registration

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a10391-6355-7b41-b0fa-3e14e874f091
2026-10-04 12:11:47 +02:00

1.7 KiB
Raw Blame History

id type title domain repo status owner topic_slug created updated state_hub_workstream_id
ACTIVITY-WP-ADHOC-2026-08-20 workplan Ad hoc — activity-core opportunistic fixes 2026-08-20 infotech activity-core finished codex activity-core 2026-08-20 2026-08-20 3c871564-3da4-5980-a13e-8a6145a57619

ACTIVITY-WP-ADHOC-2026-08-20 — activity-core opportunistic fixes

Reconcile the daily TODO review sink warning

id: ACTIVITY-WP-ADHOC-2026-08-20-T01
status: done
priority: low
state_hub_task_id: "57fb69b8-316d-5aa8-b0c9-b9126384ee8b"

The projected daily-todo-md-stale-review definition still said that IssueSink defaulted to rest and that re-enabling the definition would unconditionally recreate Forgejo issues. That warning described the state before ACTIVITY-WP-0022 and contradicted the current code, deployment configuration, and weekly-sbom-staleness definition.

Correct the warning to state that ISSUE_SINK_TYPE=state-hub is the safe fleet default, rest is explicit opt-in, and State Hub progress is visibility rather than claim authority. Keep the schedule disabled so a documentation correction does not silently change production cadence, and document the operational checks needed before it is deliberately re-enabled. Add a projection test so the stale default rest claim cannot recur unnoticed.

Verification:

  • Focused regression and IssueSink tests: 7 passed.
  • Full suite: 342 passed, 1 skipped, 4 failed. The four failures are unrelated existing inconsistencies: rules boundary allowlisting, the State Hub image pin assertion, a schedule-health response double missing status_code, and the sync-service expectation omitting the returned errors count.