Prove generic accepted work packages with rich artifacts

[bigboateng]

Summary

• Add a generic work-package proof Flow that stops at approved-package without plan semantics.
• Update product delivery to use planningPackage and promote only implementation-plan.
• Declare rich architecture, implementation, task, verification, journey, and evidence outputs without giving artifact names special behavior.
• Pin the exact Boatstack candidate runtime and SDK packages from Generalize accepted work packages operatorstack/boatstack#232.

Acceptance evidence

Fresh Cursor runs reached approved-package and approved-plan in separate worktrees and fresh controller state. Both runs rejected malformed task, verifier, command, journey, and schema candidates before accepting the valid package. Exact package verification passed individually and together with approval and current-program requirements. Generic manifests and approvals contain no plan fields; only the promotion receipt names implementation-plan, while architecture-plan remains an ordinary output.

Local verification

• npm ci
• Explicit compile and check for both Flows
• npm --prefix projects/basic-react ci
• npm --prefix projects/basic-react run check (41 tests)
• npm --prefix projects/basic-react run build
• git diff --check

No product implementation, merge, or deployment was performed.