Harden plan builder lifecycle and MCP efficiency

[jamil2018]

Summary

• repair expected-red baseline classification and retry recovery while preserving prior evidence
• align validation locator aliases and authoring guidance, and compact MCP lifecycle responses
• prevent duplicate runtime scenario events and persist correct completion state hashes
• disable actions on superseded baseline evidence and refresh lifecycle docs, contracts, tests, and Graphify outputs

Why

The supervised BeWise plan-builder happy path exposed lifecycle dead ends, oversized responses, stale validation guidance, duplicate events, and UI actions remaining available on historical evidence.

Validation

• BeWise full lifecycle completed: 4/4 scenarios and 33/33 steps
• npm run validate:unit: 926 passed
• npm --prefix packages/appraisejs run test: 121 passed
• npm --prefix packages/appraisejs run test:mcp:e2e
• npm run build
• focused ESLint checks
• npm run check:harness
• npm run release:check:artifacts
• npm run release:check:packages
• npm run graphify:auto
• pre-commit quality gates passed (React Doctor 97/100; Fallow warning-only test duplication, with no dead-code or complexity errors)

The transient BeWise audit plan/review/validation artifacts are intentionally excluded from this PR.