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

Guard Forgejo Actions pagination #420

Closed
coilyco-ops wants to merge 0 commits from issue-419 into main
pull from: issue-419
merge into: coilyco-flight-deck:main
Conversation 1 Commits - Files changed -
coilyco-ops commented 2026-07-10 09:09:05 +00:00
Owner
Copy link

closes #419

ward.workflow: pull-requests-and-merge

closes #419 ward.workflow: pull-requests-and-merge
coilyco-ops commented 2026-07-10 09:17:41 +00:00
Author
Owner
Copy link

verdict: block
confidence: high
summary: The patch adds a new safe bridge, but it leaves the existing documented Actions task listing surface intact. The original performance trap remains reachable through ward ops forgejo tasks list --limit N.
findings:

  • severity: high
    file: docs/ward-ops-forgejo-reference.md
    line: 865
    problem: The existing ward ops forgejo tasks list read surface remains documented with --page optional and --limit optional, while .ward/ward-kdl.forgejo.guardfile.kdl still exposes can list tasks. The PR adds ward ops forgejo actions tasks, but it does not adjust or fence the existing task list command that agents already see in the generated reference.
    impact: The issue contract asks for the ward Forgejo Actions read surface to default to a safe first page. After this patch, an agent can still follow the existing committed reference and run the same hazardous shape, pulling full task history when limit is used without page.
    conclusion: Review blocks PR #420. The safe bridge and tests are useful, but the dangerous existing tasks list surface still needs to be adjusted, hidden, or documented with a hard guard so callers cannot keep triggering full-history Actions pulls through the current ward ops reference.
verdict: block confidence: high summary: The patch adds a new safe bridge, but it leaves the existing documented Actions task listing surface intact. The original performance trap remains reachable through `ward ops forgejo tasks list --limit N`. findings: - severity: high file: docs/ward-ops-forgejo-reference.md line: 865 problem: The existing `ward ops forgejo tasks list` read surface remains documented with `--page` optional and `--limit` optional, while `.ward/ward-kdl.forgejo.guardfile.kdl` still exposes `can list tasks`. The PR adds `ward ops forgejo actions tasks`, but it does not adjust or fence the existing task list command that agents already see in the generated reference. impact: The issue contract asks for the ward Forgejo Actions read surface to default to a safe first page. After this patch, an agent can still follow the existing committed reference and run the same hazardous shape, pulling full task history when `limit` is used without `page`. conclusion: Review blocks PR #420. The safe bridge and tests are useful, but the dangerous existing `tasks list` surface still needs to be adjusted, hidden, or documented with a hard guard so callers cannot keep triggering full-history Actions pulls through the current ward ops reference. 
closes #419
closes #419
Merge remote-tracking branch 'origin/issue-419' into issue-419
Some checks failed
ci / gate (pull_request) Failing after 8s
Details
079f84be3e
fix: make forgejo actions tasks page literal
Some checks failed
ci / gate (pull_request) Failing after 13s
Details
dc0eecb86c
test: capture forgejo tasks list request shape
Some checks failed
ci / gate (pull_request) Failing after 10s
Details
0cb41babf0
test: assert forgejo tasks list first page
Some checks failed
ci / gate (pull_request) Failing after 13s
Details
c116dcb2b8
test: remove live forgejo tasks list check
Some checks failed
ci / gate (pull_request) Failing after 9s
Details
d5d169feb8
fix: honor forgejo workspace in ward ref lookup
Some checks failed
ci / gate (pull_request) Failing after 8s
Details
217dedd400
fix: seed ward ref from forgejo workspace
All checks were successful
ci / gate (pull_request) Successful in 8s
Details
26244b9c35
Merge remote-tracking branch 'origin/main' into issue-419
Some checks failed
ci / gate (pull_request) Successful in 10s
Details
ci / gate (push) Successful in 14s
Details
mirror-to-github / test (push) Successful in 1m11s
Details
release / test (push) Successful in 59s
Details
mirror-to-github / mirror (push) Successful in 8s
Details
release / plan-release (push) Successful in 7s
Details
release / publish-dev-base (push) Failing after 4m17s
Details
release / release (push) Has been skipped
Details
8513e4144b 
# Conflicts:
#	docs/ward-specs.md
#	tests/test_ward_specs_bundle.py
coilysiren closed this pull request 2026-07-10 18:02:30 +00:00
Some checks failed
ci / gate (pull_request) Successful in 10s
Details
ci / gate (push) Successful in 14s
Details
mirror-to-github / test (push) Successful in 1m11s
Details
release / test (push) Successful in 59s
Details
mirror-to-github / mirror (push) Successful in 8s
Details
release / plan-release (push) Successful in 7s
Details
release / publish-dev-base (push) Failing after 4m17s
Details
release / release (push) Has been skipped
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
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!420
No description provided.