Release gate: current minor release

[flyingrobots]

Release gate for the target version named by this issue's milestone.

This issue is the release milestone item. Do not move implementation slices out of their Goalpost: milestones just to place them in this release milestone.

Cut rule:

• release only from a signed tag on synced main
• platform batch work is merged to main
• docs/topics accuracy and coverage audit is complete
• release checklist and CI are green
• selected public capability goalposts are closed or explicitly deferred here
• no implementation issue for the target release remains open

Release-lane query:

• Use the concrete version label that matches this issue's milestone.

Selected goalpost:

• Goalpost: Make It a Real Platform - https://github.com/flyingrobots/wesley/milestone/23

Completed platform-batch branch evidence:

• 8b9fcc12 feat(config): add project manifest CLI
• 1808a426 ci(holmes): run schema-set matrix from manifest
• f1b3a5f7 docs(platform): document manifest and module onramp

Completed docs/signpost evidence:

• comprehensive docs/topics map landed on main
• docs/topic audit corrections landed on main
• docs signpost refresh landed on main

Remaining gate work:

• land the release-prep commit through main
• complete local release validation
• cut the release from a signed tag on synced main

[coderabbitai]

🔗 Related PRs

#623 - docs(release): record v0.1.0 publication evidence [merged]
#640 - chore(release): prepare v0.1.1 [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[flyingrobots]

Oldest-issue triage update: #64 was kept in Wesley and scheduled into v0.2.0 under Goalpost: Make It a Real Platform after a rationale comment was posted on the issue.

Rationale: contributor onboarding is valid repository/platform governance, but it is not part of the immediate residue purge. It should be handled after the current docs/backlog cleanup stops presenting stale work as live direction.

This issue now blocks the v0.2.0 release gate unless completed, moved to a later release lane, or explicitly removed from v0.2.0.

[flyingrobots]

Triage update: this pass added #125 to lane:v0.2.0 / Goalpost: Make It a Real Platform. Rationale: the issue survives only as a domain-free Wesley extension/target manifest concern; downstream target details such as Supabase, REALM, Docker, and ORM settings remain outside Wesley core.

[flyingrobots]

Triage update: this pass added #138 and #139 to lane:v0.2.0 / Goalpost: Make It a Real Platform. Rationale: they survive as generic extension-target compatibility validation/docs; target-specific matrices belong in downstream repos.

[flyingrobots]

Backlog triage update for v0.2.0.

Added or confirmed scheduled issues from the final inbox purge:

• Extend wesley.config.mjs for schemaPaths/bundleDir/rebuildOnGlobs/commentMode/dashboard #231
• Multi‑schema selective rebuild (rebuild only changed schema sets) #235
• Generated CLI reference #574
• Module authoring and loading guide #576
• Fixture module zoo #585

These are platform/config/docs/extension-surface items that make Wesley easier to operate without adding domain semantics.