coilyco-flight-deck/ward

Fork 0

Migrate the forgejo verb surface (40 leaves) into ward-kdl (supersedes coily#186) #75

New issue

Closed

opened 2026-06-09 05:58:41 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-09 05:58:41 +00:00

Owner

Depends on #73 (ward-kdl runtime). Part of coily->ward wholesale merge. Supersedes coily #186 (coilyco-bridge/coily#186).

Problem

coily is merging into ward wholesale. coily's forgejo verb surface is 40 hand-written Go leaves across cmd/coily/ops_forgejo_*.go. They migrate into ward as ward-kdl declarations, not as ported Go. This issue tracks that migration.

Old coily #186 ("backfill the forgejo OpenAPI spec, stop hand-rolling") is superseded: its design tension (safety behaviors the generator can't model) is resolved by the ward-kdl runtime (#73), and its generator question is split out into the generator/engine issue.

The 40 leaves (one commit each; grouped tickets, not per-leaf tickets)

Don't cut 40 tickets - they share one cli-guard spine, one transport, and reduce to the 8 shapes in #73. Migrate per group, one leaf per commit inside each group.

issue (ops_forgejo_issue.go + ops_forgejo_issue_label.go) - create, list, view, edit, comment, close, reopen, delete; label add/remove/set. (11)
label (ops_forgejo_label.go) - create, list, edit, delete. (4)
milestone (ops_forgejo_milestone.go) - create, list, view, edit, close, reopen, delete. (7)
release (ops_forgejo_release.go) - create, list, view, edit, delete, upload-asset (multipart, shape 7). (6)
repo (ops_forgejo_repo.go) - list, view, create, edit, fork, archive, delete; topics list/set. (9)
actions (ops_forgejo_actions.go) - task list, task logs (job-walk, shape 8). (2)
admin/doctor (ops_forgejo.go) - admin user list/create, admin auth list, doctor check. NOTE: these use the in-pod k3s kubectl exec path (runForgejo/forgejoLocalArgv), NOT the HTTP API - a second transport the ward-kdl runtime must support or these stay as-is. (4)

Total: 40 HTTP leaves + 4 exec leaves. pr create is disabled (merge straight to main) - drop or carry the disabled stub.

Safety carry-over

8 create/edit leaves carry stampPolicySkipped (metacharacter-gate opt-out): issue create/edit, label create/edit, milestone create/edit, release create/edit. Their ward-kdl decl needs the opt-out flag (#73). Every mutating leaf must opt into the 301-refusal primitive.

Sequence

#73 lands the runtime + vertical slice.
Migrate group by group (issue -> label -> milestone -> release -> repo -> actions), one leaf per commit, parity-checked against the current coily verb.
The generator (separate issue) backfills the long tail once the hand-migrated groups prove the shapes.

Acceptance

All 40 HTTP leaves declared in ward-kdl with parity to today's coily verbs.
admin/doctor exec leaves either ported (runtime supports the exec transport) or explicitly deferred with a note.
coily #186 closed as superseded.

Depends on #73 (ward-kdl runtime). Part of coily->ward wholesale merge. Supersedes coily #186 (`coilyco-bridge/coily#186`). ## Problem coily is merging into ward wholesale. coily's forgejo verb surface is 40 hand-written Go leaves across `cmd/coily/ops_forgejo_*.go`. They migrate into ward as **ward-kdl** declarations, not as ported Go. This issue tracks that migration. Old coily #186 ("backfill the forgejo OpenAPI spec, stop hand-rolling") is superseded: its design tension (safety behaviors the generator can't model) is resolved by the ward-kdl runtime (#73), and its generator question is split out into the generator/engine issue. ## The 40 leaves (one commit each; grouped tickets, not per-leaf tickets) Don't cut 40 tickets - they share one cli-guard spine, one transport, and reduce to the 8 shapes in #73. Migrate per **group**, one leaf per commit inside each group. - **issue** (`ops_forgejo_issue.go` + `ops_forgejo_issue_label.go`) - create, list, view, edit, comment, close, reopen, delete; label add/remove/set. (11) - **label** (`ops_forgejo_label.go`) - create, list, edit, delete. (4) - **milestone** (`ops_forgejo_milestone.go`) - create, list, view, edit, close, reopen, delete. (7) - **release** (`ops_forgejo_release.go`) - create, list, view, edit, delete, upload-asset (multipart, shape 7). (6) - **repo** (`ops_forgejo_repo.go`) - list, view, create, edit, fork, archive, delete; topics list/set. (9) - **actions** (`ops_forgejo_actions.go`) - task list, task logs (job-walk, shape 8). (2) - **admin/doctor** (`ops_forgejo.go`) - admin user list/create, admin auth list, doctor check. NOTE: these use the in-pod `k3s kubectl exec` path (`runForgejo`/`forgejoLocalArgv`), NOT the HTTP API - a second transport the ward-kdl runtime must support or these stay as-is. (4) Total: 40 HTTP leaves + 4 exec leaves. `pr create` is disabled (merge straight to main) - drop or carry the disabled stub. ## Safety carry-over 8 create/edit leaves carry `stampPolicySkipped` (metacharacter-gate opt-out): issue create/edit, label create/edit, milestone create/edit, release create/edit. Their ward-kdl decl needs the opt-out flag (#73). Every mutating leaf must opt into the 301-refusal primitive. ## Sequence 1. #73 lands the runtime + vertical slice. 2. Migrate group by group (issue -> label -> milestone -> release -> repo -> actions), one leaf per commit, parity-checked against the current coily verb. 3. The generator (separate issue) backfills the long tail once the hand-migrated groups prove the shapes. ## Acceptance - All 40 HTTP leaves declared in ward-kdl with parity to today's coily verbs. - admin/doctor exec leaves either ported (runtime supports the exec transport) or explicitly deferred with a note. - coily #186 closed as superseded.

coilysiren referenced this issue from coilyco-flight-deck/cli-guard

2026-06-10 17:32:19 +00:00

specverb expansion: label + milestone groups (all-scalar straight-shot rows) #125

coilysiren referenced this issue

2026-06-10 17:32:37 +00:00

ward-kdl: grant label + milestone groups (all-scalar straight shot, 14 verbs) #78

coilysiren referenced this issue from coilyco-flight-deck/cli-guard

2026-06-10 17:53:27 +00:00

specverb runtime primitives: query params, array bodies, --body-file, fixed-body state toggles #127

coilysiren referenced this issue

2026-06-10 17:59:41 +00:00

ward-kdl: enable the issues batch (8 verbs) on cli-guard v0.8.0 primitives #79

coilysiren referenced this issue from coilyco-flight-deck/cli-guard

2026-06-10 18:02:41 +00:00

specverb: release/repo/pr/task expansion groups + typed (map[string]any) fixed bodies #128

coilysiren referenced this issue

2026-06-10 18:04:16 +00:00

ward-kdl: grant release/repo/pr/task groups on v0.9.0 (35 verbs) #80

coilysiren referenced this issue from coilyco-flight-deck/cli-guard

2026-06-10 18:16:01 +00:00

execverb: KDL exec dialect (wrap+exec transport) for passthrough/remote-exec verbs #130

coilysiren referenced this issue

2026-06-10 18:22:15 +00:00

Adopt execverb: admin/doctor remote-exec + git slice as exec-dialect guardfiles #81

coilysiren referenced this issue

2026-06-15 15:22:05 +00:00

Epic: coily -> ward -> ward-kdl consolidation (umbrella) #91

coilysiren closed this issue

2026-06-15 15:22:13 +00:00

coilysiren commented

2026-06-15 15:22:39 +00:00

Author

Owner

Closing: all 40 HTTP leaves are declared in cmd/ward-kdl/ward-kdl.forgejo.guardfile.kdl - issues (8), issue-labels (4), labels (5), milestones (5), releases (5), repos (5), orgs (4), pulls (2), tasks (1), release-assets (1) - at parity with the coily verbs. The 4 admin/doctor exec leaves (k3s kubectl exec path) are deferred to #81 (exec-dialect runtime), as this issue's acceptance allowed. Rolled under epic #91. coilyco-bridge/coily#186 closed as superseded.

Closing: all 40 HTTP leaves are declared in `cmd/ward-kdl/ward-kdl.forgejo.guardfile.kdl` - issues (8), issue-labels (4), labels (5), milestones (5), releases (5), repos (5), orgs (4), pulls (2), tasks (1), release-assets (1) - at parity with the coily verbs. The 4 admin/doctor exec leaves (k3s kubectl exec path) are deferred to #81 (exec-dialect runtime), as this issue's acceptance allowed. Rolled under epic #91. coilyco-bridge/coily#186 closed as superseded.

coilysiren referenced this issue

2026-06-15 15:31:07 +00:00

Cut the ward binary over to the ward-kdl forgejo guardfile and retire forgejo_issue.go #92

coilysiren added this to the coily to ward to ward-kdl consolidation milestone

2026-06-15 15:31:12 +00:00