coilyco-flight-deck/agentic-os
Watch
2
0
Code Issues 73 Pull requests Projects Releases 592 Packages 1 Activity Actions

chore(recovery): anchor triaged branch archive #1025

Closed
coilyco-ops wants to merge 10 commits from recovery/2026-07-28-triaged-branch-archive into main
pull from: recovery/2026-07-28-triaged-branch-archive
merge into: coilyco-flight-deck:main
Conversation 0 Commits 10 Files changed -
coilyco-ops commented 2026-08-12 09:16:00 +00:00
Owner
Copy link

Surfaced by a fleet branch sweep. This branch was pushed but had no pull request, so the work was sitting on the forge with nothing tracking a decision about it.

Nothing has been rebased, squashed, or edited. The branch is exactly as it was.

Last commit: 2026-07-28
Unmerged commits (no patch-equivalent on main): 9
Files still differing from main: 608

  • 9a00ef17 fix(dev-base): make publish resumable on current main
  • adb7b02b fix(dev-base): make publish resumable and retryable (closes #565)
  • b9a9fd07 fix(release): land the tag and ward-specs bundle even when an image tier flakes
  • 20565ef7 feat(forgejo): add runner-token fetch overlay
  • 72dc5498 fix: derive ward config ref from sourced checkout
  • 0c5e50ea docs: refresh ward workflow prose
  • 22bddba4 chore(workflows): run maintenance jobs in dev-base
  • e5116498 chore: refresh agent id vectors
  • 14d95658 refactor: retire issue corpus renderer

Two independent checks put this outside main: no patch-equivalent commit on main, and the touched files still differ from main's current versions. Both can misfire on a branch reworked before landing, so confirm before merging. If it is obsolete, close this and delete the branch - the point was to make the decision visible.

Surfaced by a fleet branch sweep. This branch was pushed but had no pull request, so the work was sitting on the forge with nothing tracking a decision about it. Nothing has been rebased, squashed, or edited. The branch is exactly as it was. **Last commit:** 2026-07-28 **Unmerged commits (no patch-equivalent on main):** 9 **Files still differing from main:** 608 - 9a00ef17 fix(dev-base): make publish resumable on current main - adb7b02b fix(dev-base): make publish resumable and retryable (closes #565) - b9a9fd07 fix(release): land the tag and ward-specs bundle even when an image tier flakes - 20565ef7 feat(forgejo): add runner-token fetch overlay - 72dc5498 fix: derive ward config ref from sourced checkout - 0c5e50ea docs: refresh ward workflow prose - 22bddba4 chore(workflows): run maintenance jobs in dev-base - e5116498 chore: refresh agent id vectors - 14d95658 refactor: retire issue corpus renderer Two independent checks put this outside main: no patch-equivalent commit on main, and the touched files still differ from main's current versions. Both can misfire on a branch reworked before landing, so confirm before merging. If it is obsolete, close this and delete the branch - the point was to make the decision visible.
feat(forgejo): add runner-token fetch overlay
All checks were successful
ci / gate (pull_request) Successful in 12s
Details
20565ef782 
closes #453
fix(release): land the tag and ward-specs bundle even when an image tier flakes
All checks were successful
ci / gate (pull_request) Successful in 57s
Details
b9a9fd07f3 
The release job now needs plan-release alone, so the git tag, the
Forgejo release, and the ward-specs bundle land regardless of the
image publish. publish-dev-base chains off the tag instead - images
are a consequence of the tag, not a precondition - and fails
independently and loudly. Each pushed tier in dev-base-build.py
retries with backoff, so a single registry blob-write flake re-pushes
one tier instead of costing the run. Every Telegram failure alert
(the composite action and all inline workflow copies) retries its
send: run 1127's alert died on one un-retried TLS handshake timeout,
so the blocked release surfaced nowhere.

closes #490

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
fix(dev-base): make publish resumable and retryable (closes #565)
All checks were successful
ci / ward-doctor (pull_request) Successful in 15s
Details
ci / gate (pull_request) Successful in 53s
Details
adb7b02b41
fix(dev-base): make publish resumable on current main
All checks were successful
ci / ward-doctor (pull_request) Successful in 13s
Details
ci / gate (pull_request) Successful in 54s
Details
9a00ef1746
chore(recovery): anchor triaged branch archive
All checks were successful
ci / ward-doctor (pull_request) Successful in 24s
Details
ci / gate (pull_request) Successful in 1m23s
Details
033198f3b3 
Synthetic recovery anchor. Its tree matches current main. Additional parents retain the approved triaged branch tips before ordinary branch deletion.

issue-343 e5116498ca
issue-356 22bddba496
issue-362-clean2 0c5e50ead6
issue-422 72dc549868
issue-453 20565ef782
issue-490 b9a9fd07f3
issue-565 adb7b02b41
issue-573 9a00ef1746
coilysiren closed this pull request 2026-08-12 19:05:28 +00:00
All checks were successful
ci / ward-doctor (pull_request) Successful in 24s
Details
ci / gate (pull_request) Successful in 1m23s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
burndown-2026-08
Closed in the 2026-08-26 backlog burn-down. Reopen freely: state:closed label:burndown-2026-08 recovers the whole set.

  
autonomy
async-consult
 A human needs to consult on the issue to upgrade it to headless

  
autonomy
epic
 This issue has many units of sub work - its size makes it meaningfully exclusive with other autonomy types

  
autonomy
headless
 The agent can perform the work on its own

  
autonomy
live-collab
 The agent and the human need to work together in realtime

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
priority
P0
 priority tier

  
priority
P1
 priority tier

  
priority
P2
 priority tier

  
priority
P3
 priority tier

  
priority
P4
 priority tier

  
qa-fixture
Disposable issue admitted to the bounded Ward QA verification lane.

  
role/advocate
requires work from the Developer Advocate seat

  
role/director
requires work from the Portfolio Director seat

  
role/exec
requires work from the exec role

  
role/frontend
requires work from the Frontend Engineer seat

  
role/gamedev
requires work from the Game Developer seat

  
role/human
requires a person, and specifically not an agent seat

  
role/platform
requires work from the Platform Engineer seat

  
role/qa
requires work from the QA role

  
role/science
requires work from the Applied Scientist seat

  
role/sysadmin
requires work from the Systems Administrator seat

  
state
ambient
 ambient and ephemeral work, held as a maintained document rather than a queue

No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
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
coilyco-flight-deck/agentic-os!1025
No description provided.