coilyco-flight-deck/agentic-os
2
0
Fork 0
Code Issues 31 Pull requests 2 Projects Releases 230 Packages 1 Activity Actions 1

Stop committing the upstream Forgejo swagger spec in aos #437

Merged
coilyco-ops merged 8 commits from issue-435 into main 2026-07-10 18:21:29 +00:00
Conversation 1 Commits 8 Files changed 8 +410 -31874
coilyco-ops commented 2026-07-10 11:04:55 +00:00
Member
Copy link

closes #435

ward.workflow: pull-requests-and-merge

closes #435 ward.workflow: pull-requests-and-merge
fix: stop tracking forgejo swagger lock
Some checks failed
ci / gate (pull_request) Failing after 9s
Details
4c72d2fe64
chore: retrigger ci
Some checks failed
ci / gate (pull_request) Failing after 8s
Details
345b54901e
coilyco-ops commented 2026-07-10 11:11:56 +00:00
Author
Member
Copy link

WARD-OUTCOME: blocked 🛑

details workflow: pull-requests-and-merge; review summary: skipped by ~/.ward/config.yaml default Blocker: Forgejo `ci / gate` failed twice on PR #437, each time after `Repo test gate`. Local `ward exec test` and `ward exec pre-commit-all` pass on this tree. The Forgejo job log route returned 404 for runs 918 and 922, so the failing step output is not visible from the run UI. Follow-up: inspect the Forgejo runner or job-log plumbing, or rerun the PR gate once logs are reachable.
WARD-OUTCOME: blocked 🛑 <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: skipped by ~/.ward/config.yaml default Blocker: Forgejo `ci / gate` failed twice on PR #437, each time after `Repo test gate`. Local `ward exec test` and `ward exec pre-commit-all` pass on this tree. The Forgejo job log route returned 404 for runs 918 and 922, so the failing step output is not visible from the run UI. Follow-up: inspect the Forgejo runner or job-log plumbing, or rerun the PR gate once logs are reachable. </details>
fix(ward-specs): document the launch seam
Some checks failed
ci / gate (pull_request) Failing after 15s
Details
d385f46659
Merge main into issue-435
Some checks failed
ci / gate (pull_request) Failing after 11s
Details
e76e5e223a
fix(shell): include forgejo checkout path
Some checks failed
ci / gate (pull_request) Failing after 11s
Details
75403d01e4
fix(ci): support forgejo checkout path in ward bootstrap
All checks were successful
ci / gate (pull_request) Successful in 12s
Details
3d56ad238f
fix: merge main into issue-435
All checks were successful
ci / gate (pull_request) Successful in 15s
Details
69167462cb
fix: stop committing upstream forgejo swagger spec closes #435
All checks were successful
ci / gate (pull_request) Successful in 22s
Details
7ee7585bbf
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
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.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
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!437
No description provided.