specverb: multipart formData uploads + untyped-array (names) bodies; name->id dissolved #129

New issue

Closed

opened 2026-06-10 18:10:44 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-10 18:10:44 +00:00

Owner

What

The last two specverb shapes from the runtime-foundation plan (coilyco-flight-deck/ward#73):

multipart formData - in: formData params promote to flags; file types take a path streamed into a multipart/form-data body with the right boundary content type. Dry-run names the parts ("attachment": "@/path") without reading the file.
untyped-array bodies - forgejo's IssueLabelsOption declares items: {} ("ids or names"); these lower to repeatable string flags carrying names verbatim.

New rows: issue-labels list/add/set/remove, release upload-asset.

Design note

The name->id resolution primitive anticipated by the ward runtime-foundation issue is unnecessary: the modern forgejo API accepts label names directly in IssueLabelsOption and {identifier} paths, so the multi-step shape dissolves into a plain row.

Also fits coilyco-bridge/coily#159 (the generalize-name-resolution ask) - resolved upstream.

## What The last two specverb shapes from the runtime-foundation plan (https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/73): * **multipart formData** - `in: formData` params promote to flags; `file` types take a path streamed into a multipart/form-data body with the right boundary content type. Dry-run names the parts (`"attachment": "@/path"`) without reading the file. * **untyped-array bodies** - forgejo's IssueLabelsOption declares `items: {}` ("ids or names"); these lower to repeatable string flags carrying names verbatim. New rows: issue-labels list/add/set/remove, release upload-asset. ## Design note The name->id resolution primitive anticipated by the ward runtime-foundation issue is unnecessary: the modern forgejo API accepts label names directly in IssueLabelsOption and `{identifier}` paths, so the multi-step shape dissolves into a plain row. Also fits https://forgejo.coilysiren.me/coilyco-bridge/coily/issues/159 (the generalize-name-resolution ask) - resolved upstream.

coilysiren referenced this issue from a commit

2026-06-10 18:13:19 +00:00

feat(specverb): multipart formData + untyped-array bodies

coilysiren closed this issue

2026-06-10 18:13:19 +00:00

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

2026-06-10 18:14:30 +00:00

ward-kdl verb runtime foundation: 8 capability shapes + 3 safety primitives (BLOCKER) #73

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