chore: convert CE compound-engineering-v3.12.0

.last-processed

@@ -1 +1 @@
-compound-engineering-v3.11.2
+compound-engineering-v3.12.0

dist/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "ce-lite",
-  "version": "3.11.2-lite",
+  "version": "3.12.0-lite",
   "description": "Lightweight-delegation variant of compound-engineering. Agent registrations removed; specialist prompts loaded on demand from references/agent-prompts/. See https://github.com/ak2k/ce-lite.",
   "author": {
     "name": "Kieran Klaassen",
@@ -23,6 +23,6 @@
     "image-generation"
   ],
   "ce_lite": {
-    "upstream_tag": "compound-engineering-v3.11.2"
+    "upstream_tag": "compound-engineering-v3.12.0"
   }
 }

dist/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "compound-engineering",
-  "version": "3.11.2",
+  "version": "3.12.0",
   "description": "AI-powered development tools for code review, research, design, and workflow automation.",
   "author": {
     "name": "Kieran Klaassen",

dist/.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "compound-engineering",
   "displayName": "Compound Engineering",
-  "version": "3.11.2",
+  "version": "3.12.0",
   "description": "AI-powered development tools for code review, research, design, and workflow automation.",
   "author": {
     "name": "Kieran Klaassen",

dist/CHANGELOG.md

@@ -9,6 +9,18 @@ All notable changes to the compound-engineering plugin will be documented in thi
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [3.12.0](https://github.com/EveryInc/compound-engineering-plugin/compare/compound-engineering-v3.11.2...compound-engineering-v3.12.0) (2026-06-09)
+
+
+### Features
+
+* HTML-first ideation docs and a status-free plan model ([#921](https://github.com/EveryInc/compound-engineering-plugin/issues/921)) ([e74e298](https://github.com/EveryInc/compound-engineering-plugin/commit/e74e29864fbfa2f800fc3e08509e2966e4947f1e))
+
+
+### Bug Fixes
+
+* **ce-release-notes:** placeholder links ([#915](https://github.com/EveryInc/compound-engineering-plugin/issues/915)) ([b625049](https://github.com/EveryInc/compound-engineering-plugin/commit/b6250490bec4c0488d68ad66d72bd99f6edb95fd))
+
 ## [3.11.2](https://github.com/EveryInc/compound-engineering-plugin/compare/compound-engineering-v3.11.1...compound-engineering-v3.11.2) (2026-06-06)
 
 

dist/README.md

@@ -24,7 +24,7 @@ The primary entry points for engineering work, invoked as slash commands. Detail
 | Skill | Description |
 |-------|-------------|
 | [`/ce-strategy`](../../docs/skills/ce-strategy.md) | Create or maintain `STRATEGY.md` — the product's target problem, approach, persona, key metrics, and tracks. Re-runnable to update. Read as grounding by `/ce-ideate`, `/ce-brainstorm`, and `/ce-plan` when present |
-| [`/ce-ideate`](../../docs/skills/ce-ideate.md) | Optional big-picture ideation: generate and critically evaluate grounded ideas, then route the strongest one into brainstorming |
+| [`/ce-ideate`](../../docs/skills/ce-ideate.md) | Optional big-picture ideation: generate and critically evaluate grounded ideas, then route the strongest one into brainstorming. Writes the ranked ideation artifact as a single self-contained HTML file by default (human-facing); pass `output:md` for markdown (exclusive — html OR md, never both) |
 | [`/ce-brainstorm`](../../docs/skills/ce-brainstorm.md) | Interactive Q&A to think through a feature or problem and write a right-sized requirements doc before planning. Pass `output:html` to write the doc as a single self-contained HTML file instead of markdown (exclusive — md OR html, never both) |
 | [`/ce-plan`](../../docs/skills/ce-plan.md) | Create structured plans for any multi-step task -- software features, research workflows, events, study plans -- with automatic confidence checking. Pass `output:html` to write the plan as a single self-contained HTML file instead of markdown (exclusive — md OR html, never both) |
 | [`/ce-code-review`](../../docs/skills/ce-code-review.md) | Structured code review with tiered persona agents, confidence gating, and dedup pipeline |

dist/commands/ce-ideate.md

@@ -1,6 +1,6 @@
 ---
 description: "ce-ideate"
-argument-hint: "[feature, focus area, or constraint]"
+argument-hint: "[feature, focus area, or constraint] [output:md]"
 ---
 
 <!-- Generated by ce-lite converter — do not edit. Regenerate via converter/generate_commands.py. -->

dist/references/agent-prompts/manifest.json

@@ -1,6 +1,6 @@
 {
   "schema_version": 1,
-  "upstream_tag": "compound-engineering-v3.11.2",
+  "upstream_tag": "compound-engineering-v3.12.0",
   "agent_count": 43,
   "agents": [
     {

dist/skills/ce-brainstorm/references/brainstorm-sections.md

@@ -233,14 +233,13 @@ the brainstorm.
   alongside `date` and as the resume-detection key when `ce-brainstorm`'s
   Phase 0.1 scans `docs/brainstorms/` for an existing artifact to continue.
 
-### Status flip does not apply to brainstorm
-
-Unlike plans, brainstorm artifacts have no `status` field — there is no
-`active → completed` lifecycle. A brainstorm is a one-time output that
-downstream consumers (`ce-plan`, `ce-doc-review`) reference via the plan's
-`origin:` field. The `<span class="status">` HTML hook described in
-`html-rendering.md` is a plan-side mechanic and does not render on
-brainstorm artifacts.
+### No status field
+
+Brainstorm artifacts have no `status` field and no `active → completed`
+lifecycle — a brainstorm is a one-time output that downstream consumers
+(`ce-plan`, `ce-doc-review`) reference via the plan's `origin:` field. No
+CE artifact carries a mutable status; whether work shipped is derived from
+git, not stored in the doc. Do not introduce one.
 
 ### Field-name stability