Repository navigation
README release surface cleanup #551
Description
Activity
🔗 Related PRs
#475 - Merge-worthy unmerged branches into omnibus reconciliation branch [merged]
#476 - Release/v0.1.0 [merged]
#497 - chore(release): v0.0.1 [merged]
#503 - Revise README.md for clarity and additional information [merged]
#506 - chore(release): v0.0.3 [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand 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!
Closing as satisfied/obsolete after the release-surface cleanup and Node retirement. The README now has the current codec-plan release surface, the old runtime-node package matrix row is gone, and operator/release guidance points at the Rust-native preflight/release-check path. Evidence:
README.md,docs/ENTRYPOINTS.md,docs/LEGACY_NODE_MIGRATION.md, and PR #619 validation.
Migrated from a local Wesley Method backlog card after adopting METHOD v2.1.0 tracker doctrine.
docs/method/backlog/bad-code/DX_readme-release-surface-cleanup.mdbad-codelane:bad-codeDXOriginal Local Backlog Card
README release surface cleanup
bad-codeDXWhy now
The May 5 documentation audit found small but public-facing README release
surface issues: the license badge URL omits the
flyingrobots/wesleyowner,the module quick start lacks a verification/troubleshooting link, and the
@wesley/runtime-nodepackage row says0% -> Alphawhile the release branchdepends on it for shared module entry loading and trust controls.
Hill
A reader can trust the README badges, package matrix, and quick-start module
flow without cross-checking source or package internals.
Done looks like
flyingrobots/wesley@wesley/runtime-nodepackage matrix row reflects its current releaseresponsibility, or explains why its progress remains low
module-first release posture
Repo Evidence
README.mddocs/GUIDE.mddocs/ARCHITECTURE.mddocs/audit/2026-05-05_documentation-quality.md