Let's release a 0.1.0 version of lean workspace?

[lolipopshock]

@sepo-agent /answer

[sepo-agent-app]

Yes. I’d treat this as a GitHub source/template release v0.1.0, not an npm publication.

Current state:

• The root package is already named @self-evolving/lean-workspace-template, marked private, and versioned 0.1.0: package.json#L2-L5.
• The repo has validation paths for Lean, blueprint sync, starter site, and docs builds in lean.yml#L56-L83.
• The standalone site validation workflow runs npm ci, npm run check, and npm run build: deploy.yml#L27-L66.
• The checked-in Agent / Release / Prepare workflow is for the embedded Sepo runtime and is hard-gated to self-evolving/repo, so I would not use it for this template release: agent-release-prepare.yml#L6-L19.

Recommended release plan:

1. Prepare a small release PR, probably adding a root CHANGELOG.md entry for 0.1.0 and any final README/release-note polish.
2. Do not change the root version unless we decide to regenerate lock metadata; package.json and package-lock.json already say 0.1.0.
3. Run the release checks:
   • npm ci
   • npm run check
   • npm test
   • lake build
   • npm run blueprint:sync
   • npm run build
   • QUARTZ_CONTENT_ROOT=docs npm run build
4. Merge after CI is green and machine-managed blueprint files are clean.
5. Create an annotated tag v0.1.0 from main.
6. Publish a GitHub Release for v0.1.0 with notes describing this as the initial Lean Workspace template release.
7. Close this issue from the release PR or release notes.

If that matches the intent, approve an /implement run to prepare the release PR. The actual tag/GitHub Release creation should happen only after that PR is merged.

---

Sepo activity

Sepo finished — answer · 1m54s · 30 steps

Last message

Yes. I’d treat this as a GitHub source/template release v0.1.0, not an npm publication. Current state: - The root package is already named @self-evolving/lean-workspace-template, marked private, and versioned 0.1.0: [`package.jso…

Activity

• 💬 Message "I have enough context for an answer-only response: the repo is already versioned as 0.1.0, has no visible release/tag yet, and its release automation is for the embedded Sepo runtime rather than this template package."
• 📖 Read Read package.json (completed)
• 📖 Read Read agent-release-prepare.yml (completed)
• 📖 Read Read lean.yml (completed)
• 📖 Read Read deploy.yml (completed)
• 💬 Message "Yes. I’d treat this as a GitHub source/template release v0.1.0, not an npm publication. Current state: - The root package is already named @self-evolving/lean-workspace-template, marked private, and versioned 0.1.0: [`package.jso…"

---

codex | gpt-5.5/xhigh | Macmini-runner-1