[upstream-cq] sdk/python 0.13.0: propose-immediately protocol + SKILL/reflect prompt rewrites — fork must rebase plugin prompt layer

[dwinter3]

Triggering Event

• Release: sdk/python/0.13.0
• Merged PR: mozilla-ai/cq#380 — Plugin/protocol improvements
• Concurrent surface: Go SDK prompts received identical changes in the same PR (see also open issue [upstream-cq] cli/v0.9.0: Go discovery library + FooList/FooPage wire-shape convention — untracked compat surface vs #282 / #288 #289 for Go SDK tracking)

What Changed

PR #380 ("Strengthen the propose-immediately protocol and tighten field guidance") rewrites the plugin prompt specification layer:

File	Change
plugins/cq/commands/reflect.md	Protocol guidance updated
plugins/cq/skills/cq/SKILL.md	Field guidance tightened
sdk/python/src/cq/prompts/SKILL.md	Prompt rewritten (+105/-57 total across all files)
sdk/python/src/cq/prompts/reflect.md	Prompt rewritten
sdk/go/prompts/SKILL.md	Identical update (cross-SDK coordinated)
sdk/go/prompts/reflect.md	Identical update (cross-SDK coordinated)

This is a coordinated cross-SDK protocol update — both Python and Go SDKs received the same prompt/protocol changes in a single PR. The +105/-57 delta is a non-trivial semantic rewrite, not documentation cleanup.

Why It Matters for 8th-layer

• The SKILL.md and reflect.md files are the behavioral specification layer for the cq agent/plugin system. The 8th-layer fork carries its own version of these prompt files.
• Changes to the propose-immediately protocol directly affect how agents reason about and execute cq knowledge proposals — a key surface for 8th-layer-agent.
• If the fork does not rebase these prompt files, agent behavior will silently diverge from upstream cq semantics, creating an untracked FORK_DELTA on the protocol specification layer.
• The coordinated Go+Python update signals upstream treats this as a foundational protocol change, not an incidental edit.

Recommended Action

1. Diff fork prompt files against upstream: compare plugins/cq/skills/cq/SKILL.md, sdk/python/src/cq/prompts/SKILL.md, and reflect.md equivalents in 8th-layer-agent.
2. Decide rebase vs. intentional delta: If 8th-layer's propose-immediately behavior intentionally differs from upstream, document this as a FORK_DELTA. If not, rebase to pick up tightened field guidance.
3. Check Go SDK prompt files in the same pass — they received identical changes (tracked adjacently under [upstream-cq] cli/v0.9.0: Go discovery library + FooList/FooPage wire-shape convention — untracked compat surface vs #282 / #288 #289).
4. Update [upstream-cq] sdk/python 0.12.0: server consolidates TTL + scoring into SDK — fork must audit local mirrors #286 (0.12.0 TTL/scoring audit) to note that the prompt layer is now also out of date as of 0.13.0.

Related Issues

• [upstream-cq] sdk/python 0.12.0: server consolidates TTL + scoring into SDK — fork must audit local mirrors #286 — sdk/python 0.12.0: server consolidates TTL + scoring (prior Python SDK delta)
• [upstream-cq] Node discovery protocol lands in Python SDK (/.well-known/cq-node.json) — evaluate fork compat + FORK_DELTA position #282 — Node discovery protocol in Python SDK
• [upstream-cq] cli/v0.9.0: Go discovery library + FooList/FooPage wire-shape convention — untracked compat surface vs #282 / #288 #289 — Go SDK cli/v0.9.0 tracking (concurrent release wave, same PR touched Go prompts)