lore: lore/implementation-loop/issue-1647 - #1689
Conversation
… loop
Adds a red acceptance test asserting that pruneOnce deletes the per-task
GH_TOKEN_* key from agent-secrets when it sweeps an orphaned pt-* definition.
On a satellite cluster the Floor's DELETE /api/cluster/per-task-tokens/{taskId}
call targets only the central cluster-agent, so the prune loop is the sole
reclaim path — currently it does not call any secret key deletion and the key
accumulates indefinitely.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
🔍 Lore Spec Impact — advisoryThis PR touches 2 statement(s) across 1 spec(s), and changes the validating tests alongside every one of them. Feature Specification: Running Stations in Any Kubernetes Cluster · 2 statement(s)
FR4 — Liveness, recovery, and dead-agent reaping
validated by FR4 — Liveness, recovery, and dead-agent reaping
validated by 3 new statement(s) have no test link yet. Deterministic · graph @ |
|
Lore implementation-loop run failed (failed — node "tdd-round" failed) — 87a7e5f8-022e-4bed-bfd2-85e5f1716a00. |
Opened by the Lore assembly line from
lore/implementation-loop/issue-1647.Closes #1647
Lore-Task: cb1e5fa8-1de9-4ae7-83fc-7d036eb27dc8