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

New issue

Closed

opened 2026-06-10 17:53:27 +00:00 by coilysiren · 0 comments

coilysiren commented

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

Owner

What

Four runtime primitives in the specverb engine, the foundation the ward forgejo-surface migration (coilyco-flight-deck/ward#73, coilyco-flight-deck/ward#75) is blocked on:

Scalar query params promote to typed flags and encode into the URL (list filtering and pagination - the coily pain in coilyco-bridge/coily#201).
Array-of-scalar body fields promote to repeatable slice flags (--assignees a --assignees b -> ["a","b"]); previously skipped silently, which would have dropped issueCreate's assignees/labels.
--body-file supplies the whole JSON body, mutually exclusive with body flags - the gate-safe spill (file contents bypass the metachar gate, the path does not). Required-field enforcement moves from the CLI layer to request assembly so either source satisfies it.
Fixed-body state toggles - can close issues mounts a leaf PATCHing exactly {"state":"closed"} with no body flags, declared in the expansion table.

Plus a fail-closed flag-collision gate (spec input shadowing --dry-run/--query/--output/--body-file refuses to build), and the issues group rows (get/view/list/create/edit/comment/close/reopen/delete) + milestone close/reopen as the consuming surface.

Out of scope (named follow-ups in docs/specverb.md)

name->id resolution (issue label add/remove)
multipart POST (release upload-asset)

## What Four runtime primitives in the specverb engine, the foundation the ward forgejo-surface migration (https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/73, https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/75) is blocked on: * **Scalar query params** promote to typed flags and encode into the URL (list filtering and pagination - the coily pain in https://forgejo.coilysiren.me/coilyco-bridge/coily/issues/201). * **Array-of-scalar body fields** promote to repeatable slice flags (`--assignees a --assignees b` -> `["a","b"]`); previously skipped silently, which would have dropped issueCreate's assignees/labels. * **`--body-file`** supplies the whole JSON body, mutually exclusive with body flags - the gate-safe spill (file contents bypass the metachar gate, the path does not). Required-field enforcement moves from the CLI layer to request assembly so either source satisfies it. * **Fixed-body state toggles** - `can close issues` mounts a leaf PATCHing exactly `{"state":"closed"}` with no body flags, declared in the expansion table. Plus a fail-closed flag-collision gate (spec input shadowing --dry-run/--query/--output/--body-file refuses to build), and the issues group rows (get/view/list/create/edit/comment/close/reopen/delete) + milestone close/reopen as the consuming surface. ## Out of scope (named follow-ups in docs/specverb.md) * name->id resolution (issue label add/remove) * multipart POST (release upload-asset)

coilysiren referenced this issue from a commit

2026-06-10 17:58:22 +00:00

feat(specverb): query params, array bodies, --body-file, state toggles

coilysiren closed this issue

2026-06-10 17:58:22 +00:00

coilysiren referenced this issue from coilyco-flight-deck/ward

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

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

Refactor: security-pure engine + thin KDL-expressed consumers (coily/ward/cli-guard) #123