docs: define v1.0 stabilization readiness gate

[dDevAhmed]

Summary

Implements CLI-039 by converting the completed MVP backlog into an explicit v1.0 stabilization contract.

Included

• machine-readable/reviewable readiness dimensions for functional behavior, security, compatibility, documentation, release integrity, performance, and usability;
• explicit Automated / Manual / Blocked verification model;
• release-candidate policy for v0.7–v0.9;
• current Node/npm/OS support contract;
• explicit post-v1 exclusions;
• REL-001 recorded as the external npm publication blocker;
• gap-handling policy that requires newly discovered work to become separately scoped issues.

Reconciliation finding

The review identified stale installation/publication documentation. That work is intentionally separated into CLI-040 rather than hidden in this readiness PR.

Closes #90

Summary by CodeRabbit

• Documentation
  • Added a v1.0 readiness checklist for the StellarForge CLI.
  • Documented functional, security, compatibility, performance, release, and stabilization criteria.
  • Defined readiness statuses, blocker handling, supported environments, and final release-decision requirements.
  • Documented scope limits for stabilization releases and potential post-v1 candidates.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 0b1b81b3-9ac8-49e3-ac26-741fb911649b

📥 Commits

Reviewing files that changed from the base of the PR and between 665e4d4 and 729b615.

📒 Files selected for processing (1)

• docs/roadmap/v1-readiness.md

---

📝 Walkthrough

Walkthrough

The pull request adds a v1.0 readiness contract for StellarForge CLI. It defines required checks, supported environments, release criteria, stabilization limits, known blockers, post-v1 scope, and final readiness conditions.

Changes

v1.0 readiness

Layer / File(s)	Summary
Readiness contract docs/roadmap/v1-readiness.md	Defines functional and security checks, supported Node.js versions and operating systems, documentation and release requirements, performance targets, stabilization rules, post-v1 scope, the REL-001 publication blocker, gap handling, and final release criteria.

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

Change: Other

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/cli-039-v1-readiness

---

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