cupertino-longevitylisted

Judge whether this architecture can evolve, or whether it is quietly building toward a forced rewrite (a "Vista Trap" — a decision that looks fine today but has no incremental path forward, the way Windows Vista's restart-from-scratch approach differed from the unbroken NeXTSTEP → macOS → Apple Silicon line). ## Steps 1. **Vista Trap Table**: list concrete decisions under consideration or already made, and for each, name the specific way it could force a rewrite rather than an incremental upgrade (a hardcoded assumption, a leaky abstraction, a dependency with no exit path). 2. **Evolution Readiness Score** — exactly 6 dimensions, each scored 1–5: - API/interface stability - Data model flexibility - Dependency exit costs - Test/characterization coverage of current behavior - Deployment/rollback reversibility - Team knowledge concentration (bus-factor risk) Compute the total mechanically — do not eyeball whether the roadmap is needed: ```bash echo '{"dimensionScores": [d1, d2, d3, d4, d5, d6]}' | python3 "${CLAUDE_PLUGIN_ROOT}/scripts/validators.py" evolution-score ``` The script rejects any call that doesn't supply exactly 6 integer scores from 1–5, and returns `rosettaRoadmapRequired` computed against the fixed threshold of 18 — total < 18 requires a Rosetta Roadmap, total ≥ 18 must NOT include one. Follow whatever the script returns; do not override it with judgment either direction. 3. **Vista Countdown**: give a dated forecast of when th