[aitrawog]

Summary

charly candy params plugin-cua --check — the drift gate this repo's candy binds and its CI runs — FAILS on
main: the committed projection still carries the older json:-only struct-tag shape, while the pinned
generator (charly's provisioned cue v0.16.1, cue exp gengotypes) emits both yaml: and
json: tags. This PR is the regeneration: the committed projection is replaced with exactly what
the schema generates, tag for tag.

 candy/plugin-cua/params/cue_types_gen.go | 76 ++++++++++++++++----------------
 1 file changed, 38 insertions(+), 38 deletions(-)

No hand edits: the file is the generator's output, byte for byte.

The branch was preserved during a branch/worktree backlog cleanup and is being upstreamed unchanged. Head is
d86cfc84a0ebad9d4ce3fabccdb366ef7d669f4f, authored before this session, never amended, rewritten or force-pushed; it was already on
origin at exactly this SHA, so no push was required or made.

How tested

Own gate, PR head — rc=0:

$ charly -C <root>/.worktrees/drift-113/plugin-cua candy params plugin-cua --check
rc=0

Negative control, base — rc=1, which is the defect this PR removes. The base-side command runs against the repo's main checkout, which is at origin/main (a78445b).

$ charly -C <root>/plugin-cua candy params plugin-cua --check
charly: error: command "candy": ... is STALE: it differs from what .../schema generates — run `charly candy params plugin-cua` and commit the result
rc=1

Repo-declared build gate (AGENTS.md), same head — all rc=0:

$ (cd candy/plugin-cua && go build ./...)
rc=0
$ (cd candy/plugin-cua && gofmt -l .)
rc=0
$ (cd candy/plugin-cua && go vet ./...)
rc=0
$ (cd candy/plugin-cua && go test ./...)
ok  	github.com/opencharly/plugin-cua/candy/plugin-cua	0.004s
rc=0

$ charly -C <worktree> box validate
charly box validate: OK — checked 1 candy, 2 deploys, 7 distros, 7 builders; 0 warnings, 0 errors
rc=0

Rulebook compliance

• R0 — skills loaded before the first git/PR action (git-workflow), and this repo's own AGENTS.md read first: its Build / validate / test section is the gate pasted above.
• R1 — no finding to classify: every command above returns 0 with zero warnings; the base-side rc=1 is the defect this PR removes, and it is fixed here rather than filed.
• R2 — no duplication: the projection is generated from candy/plugin-cua/schema/*.cue by the one generator (charly candy params); nothing hand-written is added beside it.
• R3 — no workaround: no hand edit, no suppression, no retry, no dual shape — the file is the generator's own output and the gate is the same command CI runs.
• R4 — product before prose: no documentation is changed to route around anything; the artifact is corrected at its source (schema → generated file).
• R5 — legacy deleted completely: the stale shape is replaced wholesale, with no shim and no compatibility path left behind.
• R6 — git status was read first; the branch already stood at this exact SHA on origin, so nothing was pushed, amended, rewritten or force-pushed; main is untouched and no other session's work is edited.
• R7 — the check FAILS without the change and passes with it (rc=1 at the base, rc=0 at the head — both pasted), and the emitted artifact is validated at its actual boundary: the same generator that writes the file is the one that judges it.
• R8 — N/A — no live service boundary is crossed: the change is a generated Go type projection, and nothing here is mocked, stubbed or faked.
• R9 — N/A — no binary is rebuilt and no runtime OS dependency is added; the diff touches only the generated projection (and, where noted, a test or the candy's own plan:).
• R10 — not run, and not claimed: no disposable: true bed was run in this round. For a generated-projection regeneration the owning gate is the drift check pasted above; this body claims syntax check only, not a live validation.

Change classification

Generated artifact; no hand edits. candy/plugin-cua/params/cue_types_gen.go is produced by charly candy params plugin-cua from candy/plugin-cua/schema/*.cue, and this PR commits the generator's current output. There is no schema
change, no capability change, no label change and no runtime dependency.

Rollback: git revert the commit on this branch — the previous projection returns and the drift gate goes back
to failing, which is precisely the state main is in today. Nothing to migrate, no data, no consumers to coordinate.

Assisted-by: DeepSeek Harness deepseek-v4.1-flash (syntax check only)

[github-actions]

Review — PASS

The PR changes exactly one file, candy/plugin-cua/params/cue_types_gen.go, and the diff is limited to adding yaml: struct tags alongside the existing json: tags on CuaInput and CuaDeviceInput. No field names, types, comments, schema inputs, or runtime logic are altered.

• The stated file count and +38/-38 diff size match the provided diff.
• The change is consistent with the body’s claim that the committed generated projection was stale relative to the pinned generator output.
• No legacy JSON-only shape remains in the touched structs.
• No secrets, unsafe input handling, dependency changes, or privilege changes are introduced.
• The drift gate described in the body is the appropriate validation for a generated artifact; no additional hand-written test is required for this tag-only regeneration.
• There are no comments to disposition.

The Method field’s yaml:"method,omitempty" versus json:"method" asymmetry is generator-shaped rather than a hand-written semantic change, and does not create a runtime or security concern on its own.

Verdict: PASS

---

ollama-cloud/deepseek-v4.1-flash — action-review.

View action run