docs: record why the issue/label agent pipeline was abandoned #28
No reviewers
Labels
No labels
agent
coordinate
agent
dev
agent
plan
agent
reflect
agent
test
agent
triage
ai/off
blocked
night
blocked
usage
loop
1
loop
2
loop
3
needs/approval
needs/human
needs/input
needs/review
plan/approved
run/night
state
blocked
state
building
state
passed
state
planning
state
testing
tier
fable
tier
haiku
tier
local
tier
opus
tier
sonnet
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
valssi-public/agent-workflows!28
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/abandonment-rationale"
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?
Follow-up to #27. The 2026-09-29 DECISIONS entry said "the rationale beyond 'no longer used' is not recorded". It now records your five reasons:
Each reason has a one-line concrete example. The examples are mine, taken from this repo's own history: the
secrets:-under-workflow_calland bare composite-action-ref failures, the duplicate caller that doubled every run, logs that only the web UI can show, and preflight blocks that exit green. Trim them if you'd rather keep only the headline reasons.The entry still notes that the replacement approach is not recorded. CHANGELOG entry added.
🤖 Generated with Claude Code