fix(release): update EXPECTED_GUIDES, sync templates, clean lockfile for v0.9.0

- Add 5 new guide pages to EXPECTED_GUIDES array in docs-build test
- Sync squad.agent.md template (removed Task Context Signal section)
- Clean package-lock.json for v0.9.0 release

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: Copilot

.github/agents/squad.agent.md

@@ -154,23 +154,9 @@ For each squad member with assigned issues, note them in the session context. Wh
 
 **The user should never see a blank screen while agents work.** Before spawning any background agents, ALWAYS respond with brief text acknowledging the request. Name the agents being launched and describe their work in human terms — not system jargon. This acknowledgment is REQUIRED, not optional.
 
-#### Task Context Signal
-
-Before naming agents, classify how this message relates to the conversation so far. This helps users understand whether the system sees continuity or a fresh start. Use exactly one of these signals as the **first line** of your acknowledgment:
-
-- 🔗 **Continuing** `{brief context}` — the message extends the same task thread (e.g., a follow-up question, next step, or refinement of earlier work)
-- 🆕 **New task** — the message is unrelated to previous work in this session
-- 🔀 **Related pivot** `{brief context}` — the message connects to earlier work but shifts focus to a different concern
-
-Skip the signal only on the very first message of a session (there's no prior context to classify against).
-
-#### Agent Launch
-
-- **Single agent:** `"🔗 Continuing your auth refactor\nFenster's on it — looking at the error handling now."`
-- **Multi-agent spawn:** Show the signal, then a quick launch table:
+- **Single agent:** `"Fenster's on it — looking at the error handling now."`
+- **Multi-agent spawn:** Show a quick launch table:
   ```
-  🔀 Related pivot from the auth work — now looking at tests
-
   🔧 Fenster — error handling in index.js
   🧪 Hockney — writing test cases
   📋 Scribe — logging session

package-lock.json

@@ -173,7 +173,7 @@
     "node": ">=22.5.0"
   },
   "dependencies": {
-    "@bradygaster/squad-sdk": "*",
+    "@bradygaster/squad-sdk": "file:../squad-sdk",
     "ink": "^6.8.0",
     "react": "^19.2.4",
     "vscode-jsonrpc": "^8.2.1"

packages/squad-cli/package.json

@@ -1185,7 +1185,7 @@ This runs as a standalone local process (not inside Copilot) that:
 |-------|------|-----|
 | **In-session** | You're at the keyboard | "Ralph, go" — active loop while work exists |
 | **Local watchdog** | You're away but machine is on | `npx @bradygaster/squad-cli watch --interval 10` |
-| **Cloud heartbeat** | Fully unattended | `squad-heartbeat.yml` GitHub Actions cron |
+| **Cloud heartbeat** | Fully unattended | `squad-heartbeat.yml` — event-based only (cron disabled) |
 
 ### Ralph State
 

packages/squad-sdk/templates/squad.agent.md

@@ -17,7 +17,7 @@ const DIST_DIR = join(DOCS_DIR, 'dist');
 // Expected content directories in src/content/docs/
 const EXPECTED_GET_STARTED = ['installation', 'first-session', 'five-minute-start', 'choosing-your-path', 'migration'];
 
-const EXPECTED_GUIDES = ['tips-and-tricks', 'sample-prompts', 'personal-squad', 'contributing', 'contributors', 'shell'];
+const EXPECTED_GUIDES = ['build-autonomous-agent', 'building-extensions', 'contributing', 'contributors', 'extensibility', 'faq', 'github-auth-setup', 'personal-squad', 'sample-prompts', 'shell', 'tips-and-tricks'];
 
 const EXPECTED_REFERENCE = ['cli', 'sdk', 'config', 'api-reference', 'integration', 'tools-and-hooks', 'glossary'];