Lab #643: model delete --json output shape doesn't match the documented {deleted, modelId, modelName, artifactsDeleted}

Summary

The documented output shape for swamp model delete --json does not match what the CLI actually returns.

The reference docs (.claude/skills/swamp/references/model/guide.md, "Delete a Model") document this shape:

{
  "deleted": true,
  "modelId": "<uuid>",
  "modelName": "<name>",
  "artifactsDeleted": { "outputs": 5, "dataItems": 3 }
}

The CLI actually returns:

{
  "deleted": {
    "id": "<uuid>",
    "name": "<name>",
    "type": "<model-type>",
    "inputPath": "<repo>/models/<type>/<uuid>.yaml"
  },
  "resourceDeleted": false,
  "outputsDeleted": 0,
  "evaluatedInputDeleted": false,
  "dataDeleted": false
}

So: deleted is an object, not a boolean; there is no modelId / modelName / artifactsDeleted; and the artifact counts are spread across resourceDeleted / outputsDeleted / evaluatedInputDeleted / dataDeleted.

Environment

swamp 20260611.205205.0-sha.ad439a70 (latest; swamp update --check reports up_to_date)
macOS, arm64
Reproduced with a freshly created and deleted model (behavior is model-type-independent).

Steps to reproduce

swamp model create <type> delete-shape-test --json
swamp model delete delete-shape-test --json

Impact

Agents and scripts following the documented shape parse .deleted == true / .modelName and get nulls, making a successful delete look like a failure and requiring a follow-up model search to confirm deletion.

Suggested fix

Either update the reference doc to the actual shape, or (better for stability) emit the documented shape: a boolean deleted, the model name/id at top level, and an artifactsDeleted rollup.

extension push: issue-verdict review is indistinguishable from missing/stale

Document model-method data-mutation surface (dataRepository.delete, findAllForModelSince, queryData)

@swamp/aws/cloudformation: expose StackSet instances, drift, and operations (Cloud Control cannot)

extension push: adversarial-review report hash is platform-dependent (macOS vs Linux), so committed reviews never match a cross-OS runner

model search --json returns a bare model object instead of {query, results} when exactly one model matches

model delete --json output shape doesn't match the documented {deleted, modelId, modelName, artifactsDeleted}

Extension API: allow export const extension to add resource specs, or document that it cannot

Add a way to list registered report definitions (report search only lists results)

workflow validate: method args with a Zod .default() are treated as required

extension quality scorer mis-detects quoted phrases in comments as bare imports

Support CI-friendly adversarial review artifacts for extension push

extension push --dry-run --json reports local helper imports as bogus model entries

Extension source: direct-content export scan only reads first 64 KiB, silently drops exports beyond it

Managed skills ship with dangling reference-doc links

Add a list/discover method to dbcluster for enumerating clusters in a region

workflow-scope report's dataRepository.getContent returns null for data written in the same workflow run

dbcluster state schema is missing DBClusterMembers (writer/reader, instance class)

workflow direct-execution inputs.* persist as globalArguments on auto-definitions and freeze on first run

Workflow validation should resolve modelType for direct-execution steps

bucket-policy StateSchema.PolicyDocument declared z.string() but CloudControl returns it as a parsed object

bucket-policy GlobalArgsSchema requires Bucket and PolicyDocument, blocking workflow-YAML direct execution of get

Report execute throws are advisory: workflow marked succeeded, exit 0, AND report output is discarded

dataRepository.getContent rejects string type in production but docs and testing helper demonstrate strings

Relationships

#643 model delete --json output shape doesn't match the documented {deleted, modelId, modelName, artifactsDeleted}