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

coilyco-flight-deck:main

coilyco-flight-deck:release

coilyco-flight-deck:issue-573

coilyco-flight-deck:issue-568

coilyco-flight-deck:issue-565

coilyco-flight-deck:issue-454

coilyco-flight-deck:issue-561

coilyco-flight-deck:issue-556-replacement

coilyco-flight-deck:issue-553

coilyco-flight-deck:issue-539-profile-substrate

coilyco-flight-deck:issue-454-v2

coilyco-flight-deck:issue-505

coilyco-flight-deck:issue-504

coilyco-flight-deck:issue-501

coilyco-flight-deck:issue-499

coilyco-flight-deck:issue-496

coilyco-flight-deck:issue-491

coilyco-flight-deck:issue-490

coilyco-flight-deck:issue-488

coilyco-flight-deck:issue-486

coilyco-flight-deck:feat/two-stage-release

coilyco-flight-deck:fix/comment-cap-and-pr-gate

coilyco-flight-deck:feat/sync-actions-secrets

coilyco-flight-deck:fix/actions-logs-bridge

coilyco-flight-deck:fix/launch-config-stability

coilyco-flight-deck:fix/defaults-are-wards-not-aos

coilyco-flight-deck:experiment/no-ops-forgejo

coilyco-flight-deck:fix/ci-pytest-gate-and-repos-kdl

coilyco-flight-deck:issue-434

coilyco-flight-deck:issue-447

coilyco-flight-deck:issue-453

coilyco-flight-deck:issue-450

coilyco-flight-deck:issue-446

coilyco-flight-deck:issue-435

coilyco-flight-deck:issue-393

coilyco-flight-deck:issue-268

coilyco-flight-deck:issue-438

coilyco-flight-deck:issue-397

coilyco-flight-deck:issue-431

coilyco-flight-deck:issue-427

coilyco-flight-deck:issue-425

coilyco-flight-deck:issue-421

coilyco-flight-deck:issue-422

coilyco-flight-deck:issue-403

coilyco-flight-deck:issue-805

coilyco-flight-deck:issue-355

coilyco-flight-deck:issue-362-clean2

coilyco-flight-deck:issue-356

coilyco-flight-deck:issue-343

coilyco-flight-deck:issue-315

coilyco-flight-deck:issue-223

Conversation 1 Commits - Files changed -

coilyco-ops commented 2026-07-10 09:09:05 +00:00

Member

Copy link

closes #419

ward.workflow: pull-requests-and-merge

closes #419 ward.workflow: pull-requests-and-merge

coilyco-ops added 1 commit 2026-07-10 09:09:06 +00:00

guard forgejo actions pagination 8d75f48b1f

coilyco-ops commented 2026-07-10 09:17:41 +00:00

Author

Member

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.

coilyco-ops added 1 commit 2026-07-10 10:31:37 +00:00

fix forgejo actions tasks pagination ... d8e540cde8

closes #419

coilyco-ops added 3 commits 2026-07-10 10:45:58 +00:00

guard forgejo actions pagination a02213d818

fix forgejo actions tasks pagination ... f37910d74c

closes #419

Merge remote-tracking branch 'origin/issue-419' into issue-419 079f84be3e

coilyco-ops added 1 commit 2026-07-10 10:54:55 +00:00

fix: make forgejo actions tasks page literal dc0eecb86c

coilyco-ops added 1 commit 2026-07-10 10:55:42 +00:00

test: capture forgejo tasks list request shape 0cb41babf0

coilyco-ops added 1 commit 2026-07-10 10:57:05 +00:00

test: assert forgejo tasks list first page c116dcb2b8

coilyco-ops added 1 commit 2026-07-10 10:59:17 +00:00

test: remove live forgejo tasks list check d5d169feb8

coilyco-ops added 1 commit 2026-07-10 11:03:06 +00:00

fix: honor forgejo workspace in ward ref lookup 217dedd400

coilyco-ops added 1 commit 2026-07-10 11:04:06 +00:00

fix: seed ward ref from forgejo workspace 26244b9c35

coilyco-ops added 1 commit 2026-07-10 16:31:16 +00:00

Merge remote-tracking branch 'origin/main' into issue-419 ... 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

coilyco-ops referenced this pull request 2026-07-14 07:55:55 +00:00

Repair agentic-os PR merge queue blocked by base-branch conflicts #445

Some checks failed

Hide all checks

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

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

  

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

Subscribe

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.