[upstream-cq] cli/v0.10.0: Go SDK + CLI plugin prompt layer rewrites for propose-immediately — untracked surface beyond #329

[dwinter3]

Triggering Event

https://github.com/mozilla-ai/cq/releases/tag/cli/v0.10.0

What Changed

PR mozilla-ai#380 — Plugin/protocol improvements

"Strengthen the propose-immediately protocol and tighten field guidance."

Files changed (105 additions / 57 deletions):

• plugins/cq/commands/reflect.md — CLI plugin command layer
• plugins/cq/skills/cq/SKILL.md — CLI plugin skill definition
• sdk/go/prompts/SKILL.md — Go SDK prompt layer (net-new surface vs [upstream-cq] sdk/python 0.13.0: propose-immediately protocol + SKILL/reflect prompt rewrites — fork must rebase plugin prompt layer #329)
• sdk/go/prompts/reflect.md — Go SDK prompt layer (net-new surface vs [upstream-cq] sdk/python 0.13.0: propose-immediately protocol + SKILL/reflect prompt rewrites — fork must rebase plugin prompt layer #329)
• sdk/python/src/cq/prompts/SKILL.md — Python SDK (overlaps [upstream-cq] sdk/python 0.13.0: propose-immediately protocol + SKILL/reflect prompt rewrites — fork must rebase plugin prompt layer #329)
• sdk/python/src/cq/prompts/reflect.md — Python SDK (overlaps [upstream-cq] sdk/python 0.13.0: propose-immediately protocol + SKILL/reflect prompt rewrites — fork must rebase plugin prompt layer #329)

PR mozilla-ai#383 — Update version of Go SDK used in CLI

• cli/go.mod / cli/go.sum bumped to pick up Go SDK with new prompt content.

Why This Matters for 8th-layer

This is additive to #329, not duplicative. Issue #329 scoped the prompt rewrite to the Python SDK (sdk/python 0.13.0). This release canonicalizes the same propose-immediately protocol strengthening at two additional layers:

1. Go SDK prompt layer (sdk/go/prompts/SKILL.md, sdk/go/prompts/reflect.md) — this surface has no prior tracking issue. If the fork has any Go-side plugin/protocol harness, it must rebase against these rewrites.
2. CLI plugin layer (plugins/cq/commands/reflect.md, plugins/cq/skills/cq/SKILL.md) — the canonical plugin definitions shipped with the CLI have changed field guidance. Forks shipping or wrapping the upstream CLI plugin definitions need to audit.

The Go SDK bump in cli/go.mod (PR mozilla-ai#383) confirms these prompt changes are now load-bearing at runtime in the CLI — not speculative.

Note: Issue #330 exists but contains only a shallow auto-generated summary with no engineering action items; this issue provides the necessary detail.

Relationship to Open Issues

• Extends [upstream-cq] sdk/python 0.13.0: propose-immediately protocol + SKILL/reflect prompt rewrites — fork must rebase plugin prompt layer #329 (Python SDK 0.13.0 prompt rewrite) — Go SDK and CLI plugin layers now need equivalent audit
• Supersedes thin tracking in [cq-align] The cq team released version 0.10.0 of their command-line tool with improvements to the plugin system and communication protocol. #330
• CLI predecessor tracked in [upstream-cq] cli/v0.9.0: Go discovery library + FooList/FooPage wire-shape convention — untracked compat surface vs #282 / #288 #289 (v0.9.0, wire-shape) — different surface, not a continuation

Recommended Actions

1. Diff sdk/go/prompts/SKILL.md and sdk/go/prompts/reflect.md against any Go-side prompt or skill definitions in the fork
2. Audit plugins/cq/skills/cq/SKILL.md and plugins/cq/commands/reflect.md if the fork ships or repackages upstream CLI plugins
3. Cross-reference with [upstream-cq] sdk/python 0.13.0: propose-immediately protocol + SKILL/reflect prompt rewrites — fork must rebase plugin prompt layer #329's Python-layer audit — if the fork's plugin prompt layer is language-agnostic or shared, a single combined rebase may be possible
4. Determine FORK_DELTA position: does the fork intentionally deviate from upstream propose-immediately field guidance, or should it track upstream?