docs(blog): add reusable machine journal

[simple-agent-manager]

Summary

Publishes SAM's September 12 technical journal entry. It explains, in plain language, how SAM now keeps compatible VMs reusable across ordinary deployments and waits briefly for a VM that is only busy building another workspace, rather than immediately provisioning another machine.

The post includes a Mermaid placement-flow diagram and extends the existing browser regression matrix to render and exercise its controls.

Validation

• pnpm --filter @simple-agent-manager/www lint
• pnpm --filter @simple-agent-manager/www typecheck (existing baseline: 4 errors, 0 warnings, 17 hints)
• pnpm --filter @simple-agent-manager/www test (49 passed)
• pnpm --filter @simple-agent-manager/www check:links (0 broken internal links)
• pnpm --filter @simple-agent-manager/www build
• pnpm exec playwright test tests/playwright/blog-mermaid.spec.ts --project='Desktop Chrome' (7 passed, including the new journal)
• git diff --check origin/main...HEAD

Staging Verification

N/A: docs-only public-site content and a browser-test matrix update. No runtime application code, API contract, infrastructure, or deployment configuration changed. The local Playwright test renders the post and verifies the interactive Mermaid viewport, controls, and horizontal-overflow guard.

UI Compliance Checklist

N/A: this changes blog content and its existing browser regression matrix; it does not change an app or site UI component. I reviewed the generated desktop screenshot for the new post; the diagram and page rendered without clipping or horizontal overflow.

End-to-End Verification

N/A: no application data flow changed. The static-site build generated /blog/sams-journal-a-busy-machine-can-still-help/, and the Playwright test opened that route in Chromium.

Post-Mortem

N/A: content-only PR.

Specialist Review Evidence

• All local reviewers completed and findings addressed before merge

Reviewer	Status	Outcome
task-completion-validator	PASS	Research, checklist, and acceptance criteria map to the blog post, Mermaid regression entry, and validation evidence. UI/data-path and multi-resource checks are not applicable.
doc-sync-validator	PASS	No API, configuration, or architecture contract changed. Public-site build and internal link validation pass; source links identify the merged technical work.

CodeRabbit Review Evidence

• coderabbit-review label applied after CI gates pass
• All CodeRabbit findings implemented or explicitly reviewed and closed/resolved
• Latest CodeRabbit review has no unresolved feedback

CodeRabbit Notes

The label triggered coderabbit-bot-review.yml run 34702713145. CodeRabbit approved
the final commit 546907eda1be6e32cdeb6df3390c8aa258387270 with no review body or
inline comments; the PR has zero unresolved review threads.

Agent Preflight

• Preflight completed before code changes

Classification

• public-surface-change
• docs-sync-change

External References

N/A: the post is based on merged commits, task conversations, and code in this repository.

Codebase Impact Analysis

• apps/www/src/content/blog/: one public devlog post.
• apps/www/tests/playwright/blog-mermaid.spec.ts: browser coverage for the new Mermaid post.
• tasks/archive/: completed task record.

Documentation & Specs

Added the public blog post. No architecture, API, self-hosting, or configuration document needs changes because no platform behavior changed in this PR.

Constitution & Risk Check

Checked that the post is accurate against merged code and contains only public technical information. No hardcoded runtime values, credentials, configuration, or product behavior are introduced.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 50c7fdf6-ee4d-42aa-94f1-6fc1b944e32c

📥 Commits

Reviewing files that changed from the base of the PR and between 4460ed9 and 546907e.

📒 Files selected for processing (3)

• apps/www/src/content/blog/sams-journal-a-busy-machine-can-still-help.md
• apps/www/tests/playwright/blog-mermaid.spec.ts
• tasks/archive/2026-09-12-sam-reusable-machine-journal.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

This change adds a SAM journal about VM-agent identity and reusable-machine scheduling. It documents bounded waiting for compatible busy machines, adds a Mermaid decision diagram, records staging validation, and includes the post in Playwright coverage.

Changes

Reusable machine journal

Layer / File(s)	Summary
Journal content and validation tasks/archive/2026-09-12-sam-reusable-machine-journal.md, apps/www/src/content/blog/sams-journal-a-busy-machine-can-still-help.md, apps/www/tests/playwright/blog-mermaid.spec.ts	The task defines the journal requirements. The post documents VM-agent identity, bounded waiting, hard refusals, and staging validation. The Playwright fixture adds the post and screenshot identifier.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 54690

This documentation-focused change adds no runtime, API, infrastructure, or deployment behavior, and is ready to merge after normal checks.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise, clear, and accurately describes the primary change: adding a reusable-machine blog journal.
Description check	✅ Passed	The description is mostly complete. It includes the change summary, validation results, docs-only staging rationale, UI and end-to-end applicability, review evidence, and preflight details. The remain…
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch sam/daily-blog-post-6q0a6b

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the waiting queue,
The busy machine helps anew.
A careful clock counts minutes by,
Then tests the path beneath the sky.
The journal hops to staging true.}

_{Comment @coderabbitai help to get the list of available commands.}

[raphaeltm]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud