Add evidence-bounded project delivery loop

[cloudsbeyond]

Summary

• Add a lightweight project delivery-loop contract covering current state, target artifact or decision, next action, gate, validation evidence, and feedback routing.
• Require an evidence-bound advance | hold | rework call before execution progresses.
• Route review findings and failures into responsible-boundary rework, and restrict memory candidates to reusable, verified, or action-changing evidence.
• Add the G11 judgment fixture and keep its JSON/Markdown guide aligned with the reusable project packet.

Why

Project work could previously start from actionable wording without making delivery state, authority gates, validation evidence, or feedback closure explicit. This change makes those judgments visible while keeping alphaX a source-level collaboration function rather than introducing a runtime state machine, connector, scheduler, or approval engine.

Open-source review

• Removed internal-source and runtime-shaped details from tracked content.
• Fixed artifact-versus-decision transition semantics.
• Aligned canonical delivery-loop keys across the operating system, project workflow, packet, and G11 fixture.
• Verified every changed YAML fence and JSON fixture parses successfully.

Validation

• bash scripts/verify-alpha-source.sh
• bash scripts/verify-local-alphaX.sh
• node scripts/generate-alphaX-indexes.mjs --check
• JSON parse for trigger and judgment fixtures
• YAML parse for every changed fenced block
• Delivery-loop schema parity check across OS, workflow, packet, and G11
• git diff --check HEAD^ HEAD
• Public-boundary scan for internal links, local paths, secrets, and ignored process data

Proof boundary

The checks and G11/G04 replay support source integrity and the tested judgment change. They do not prove broad project-delivery or productivity improvement; that still requires an applied project-work run.