release: v1.1.0 stack boost (Loop v1.5.0 cross-promo)

RELEASE_NOTES_v1.1.0.md

@@ -0,0 +1,42 @@
+# v1.1.0 — Stack release (Loop + Goal)
+
+**Loops discover work on a cadence. Goals finish bounded tasks.**
+
+This release cross-links with [Loop Engineering v1.5.0](https://github.com/cobusgreyling/loop-engineering/releases/tag/v1.5.0) — the discovery layer (`loop-sync`, `loop-constraints`, MCP server) pairs with this repo's finish layer (`/goal`, `goal-verifier`, G0→G3).
+
+## Quickstart — the stack
+
+```bash
+# Morning: loop triage
+npx @cobusgreyling/loop-init . --pattern daily-triage --tool grok
+npx @cobusgreyling/loop-audit . --suggest
+
+# Afternoon: finish top item from STATE.md
+npx @cobusgreyling/goal init . --pattern fix-bug --tool grok
+npx @cobusgreyling/goal doctor . --suggest
+```
+
+In Grok Build:
+
+```
+/goal Read STATE.md top priority. Done when verifier PASS. goal-verifier before completed: true.
+```
+
+## What's in this repo
+
+| Tool | Command |
+|------|---------|
+| **goal** (meta CLI) | `npx @cobusgreyling/goal doctor . --suggest` |
+| goal-audit | `npx @cobusgreyling/goal-audit . --json --min-level G2` |
+| goal-init | `npx @cobusgreyling/goal-init . --pattern tests-green --tool grok` |
+| goal-cost | `npx @cobusgreyling/goal-cost --pattern fix-bug` |
+
+- 6 patterns: tests-green, fix-bug, implement-feature, migrate-module, refactor-safely, coverage-target
+- [Golden path replay](examples/golden-path/SESSION.md) — 10 min end-to-end
+- [Stack cookbook](docs/stack-cookbook.md) — full day rhythm with loops
+- [Goal vs Loop](docs/goal-vs-loop.md) — when to use which primitive
+
+## Companion repos
+
+- [Loop Engineering v1.5.0](https://github.com/cobusgreyling/loop-engineering/releases/tag/v1.5.0) — scheduled discovery + triage
+- [Fleet Engineering](https://github.com/cobusgreyling/fleet-engineering) — governed agent populations

docs/goal-vs-loop.md

@@ -25,7 +25,15 @@ Do you know what "done" looks like?
 
 ## Combined Pattern (Recommended)
 
-Production setups often use **both**:
+Production setups often use **both**. [Loop Engineering v1.5.0](https://github.com/cobusgreyling/loop-engineering/releases/tag/v1.5.0) ships the discovery layer (`loop-sync`, `loop-constraints`, MCP server); this repo ships the finish layer (`/goal`, `goal-verifier`). Full day rhythm: [stack-cookbook.md](stack-cookbook.md).
+
+```bash
+# Morning: loop triage (loop-engineering)
+npx @cobusgreyling/loop-init . --pattern daily-triage --tool grok
+
+# Afternoon: finish top item (goal-engineering)
+npx @cobusgreyling/goal init . --pattern fix-bug --tool grok
+```
 
 1. **Loop** runs daily triage → writes priorities to `STATE.md`
 2. Human or loop picks top item → **`/goal`** for run-until-done execution

docs/index.html

@@ -44,6 +44,11 @@
     <img src="{{ site.baseurl }}/assets/visuals/goal-engineering-header.png" alt="Goal Engineering — Run until verifiably done" width="100%" style="max-width:640px; border-radius:12px;" />
   </p>
   <div class="badge">Grok Build /goal · update_goal · G0→G3 · 6 patterns · goal-audit CLI</div>
+  <p style="text-align:center; margin:-8px 0 20px; font-size:0.95rem;">
+    <strong>🔄 <a href="https://github.com/cobusgreyling/loop-engineering/releases/tag/v1.5.0">Loop Engineering v1.5.0</a></strong> just shipped —
+    <em>loops discover work; goals finish it.</em>
+    <a href="https://github.com/cobusgreyling/goal-engineering/blob/main/docs/stack-cookbook.md">Stack cookbook →</a>
+  </p>
   <h1>Run until<br>verifiably done</h1>
   <p class="lead">
     Goal engineering replaces one-shot prompts with persistent objectives.