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

Closed
opened 2026-06-10 17:32:19 +00:00 by coilysiren · 0 comments
Owner

What

Expand the specverb expansion table with the label and milestone groups, 5 rows each (read=get-single, list, create, edit, delete), wired to the forgejo operationIDs:

  • labels - issueGetLabel / issueListLabels / issueCreateLabel / issueEditLabel / issueDeleteLabel
  • milestones - issueGetMilestone / issueGetMilestonesList / issueCreateMilestone / issueEditMilestone / issueDeleteMilestone

Why

These are the all-scalar-body groups (CreateLabelOption, EditLabelOption, CreateMilestoneOption, EditMilestoneOption carry only scalar fields), so the full five-verb fan-out lands as pure table rows - zero engine code. This proves the straight-shot path of the migration plan before the runtime primitives (arrays, query params, state toggles) land for the harder groups.

Part of the security-pure-engine refactor (#123), feeding the ward forgejo-surface migration (coilyco-flight-deck/ward#75).

Verified

Engine unit tests pass; ward-kdl dry-runs resolve the correct method/path/body for create (POST, required fields), list (bare GET), and edit (sparse PATCH - only set fields serialized).

## What Expand the specverb expansion table with the label and milestone groups, 5 rows each (read=get-single, list, create, edit, delete), wired to the forgejo operationIDs: * labels - issueGetLabel / issueListLabels / issueCreateLabel / issueEditLabel / issueDeleteLabel * milestones - issueGetMilestone / issueGetMilestonesList / issueCreateMilestone / issueEditMilestone / issueDeleteMilestone ## Why These are the all-scalar-body groups (CreateLabelOption, EditLabelOption, CreateMilestoneOption, EditMilestoneOption carry only scalar fields), so the full five-verb fan-out lands as pure table rows - zero engine code. This proves the straight-shot path of the migration plan before the runtime primitives (arrays, query params, state toggles) land for the harder groups. Part of the security-pure-engine refactor (https://forgejo.coilysiren.me/coilyco-flight-deck/cli-guard/issues/123), feeding the ward forgejo-surface migration (https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/75). ## Verified Engine unit tests pass; ward-kdl dry-runs resolve the correct method/path/body for create (POST, required fields), list (bare GET), and edit (sparse PATCH - only set fields serialized).
Sign in to join this conversation.
No milestone
No project
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/cli-guard#125
No description provided.