Fix quality-plan project binding and evidence workflow language

[jamil2018]

What changed

• Require every MCP-created plan to be bound to an explicit registered target project and remove hub-scoped plan creation from the normal planning path.
• Update agent guidance, recovery responses, documentation, tests, and the generated MCP contract snapshot for the target-bound contract.
• Reframe the legacy baseline surface as current-state evidence and align lifecycle labels with the QA-focused Quality Plan model.
• Synchronize the create-appraisejs template and Graphify artifacts.

Why

A plan was previously created without the intended project boundary, and the plan surface still presented development-oriented baseline and implementation language. This made it possible to create an incorrectly scoped plan and obscured the QA meaning of collected evidence.

Impact

New plans fail closed until a target workspace or target identity is supplied. Existing internal baseline_* lifecycle identifiers remain compatible, while the UI presents current-state evidence and external-change terminology.

Validation

• Plan and lifecycle tests: 75 passed
• Appraise MCP package tests: 122 passed
• create-appraisejs tests: 70 passed
• Agent/swarm harness checks: passed
• Generated-artifact policy: passed
• Focused ESLint and Prettier: passed
• appraisejs package build: passed
• create-appraisejs package build and migration/seed verification: passed
• Pre-commit Fallow: passed
• Pre-commit React Doctor: 96/100, inherited warnings only