gaia-framework 1.57.0 → 1.57.2

package/_gaia/lifecycle/workflows/4-implementation/val-validate-plan/instructions.xml

@@ -1,162 +0,0 @@
-<workflow name="val-validate-plan">
-<critical>
-  <mandate>Val is READ-ONLY on the target plan artifact — never modify the plan content itself, only append findings</mandate>
-  <mandate>WRITE-ONLY to the Plan Validation Findings section — findings go to the artifact as an appended section</mandate>
-  <mandate>Classify ALL findings by severity: CRITICAL, WARNING, INFO</mandate>
-  <mandate>Always verify claims against the filesystem — no trust, no assumptions</mandate>
-  <mandate>Frame findings constructively — suggestions, not accusations</mandate>
-  <mandate>Load validation-patterns skill sections JIT per step — never pre-load the full skill</mandate>
-</critical>
-
-<step n="1" title="Load and Parse Plan">
-  <action>Load the plan artifact specified by {plan_artifact_path}</action>
-  <action>Parse the plan document and extract:
-    - All file targets with their action verbs (Create, Add, Modify, Update, Edit, Change, Fix, Delete, Remove)
-    - All version bump statements (current → planned version strings)
-    - All ADR references (e.g., ADR-012, ADR-xxx)
-    - Implementation steps with their descriptions
-  </action>
-  <action>Load validation-patterns:claim-extraction section JIT for structured claim parsing</action>
-  <action>Build a structured list of claims to verify:
-    - file_targets: [{path, action_verb, plan_step}]
-    - version_bumps: [{file, field, current_value, planned_value, plan_step}]
-    - adr_references: [{adr_id, plan_step}]
-  </action>
-  <check if="zero file targets extracted">Flag as WARNING: "Plan contains no concrete file targets — cannot verify implementation scope"</check>
-</step>
-
-<step n="2" title="File Target Verification">
-  <action>Load validation-patterns:filesystem-verification section JIT</action>
-  <action>For each file target, classify by action verb and verify:
-    - Create / Add / New / Generate → target file MUST NOT exist. If file exists: WARNING "File already exists but plan says Create — will overwrite"
-    - Modify / Update / Edit / Change / Fix → target file MUST exist. If file missing: CRITICAL "File does not exist but plan step says Modify"
-    - Delete / Remove → target file MUST exist. If file missing: WARNING "File does not exist — may have already been deleted"
-  </action>
-  <action>For each file target, run filesystem check: existsSync or equivalent verification against {project-root}</action>
-  <action>Record each finding with: severity, description, plan step reference</action>
-</step>
-
-<step n="3" title="Version Bump Verification">
-  <action>For each version bump statement found in the plan:</action>
-  <action>Parse semver strings (major.minor.patch) from both the plan text and the actual codebase files:
-    - global.yaml: framework_version field
-    - package.json: version field
-    - Any other version-bearing files referenced in the plan
-  </action>
-  <action>Compare planned version against actual current value:
-    - Sequential bump (patch +1, minor +1 with patch reset, major +1 with minor/patch reset): No finding — valid
-    - Non-sequential but valid (e.g., skip from 1.29.0 to 1.31.0): WARNING "Non-sequential version bump — skipping {skipped_version}"
-    - Major version bump (e.g., 1.x → 2.x): INFO "Major version bump from {current} to {planned} — confirm intentional"
-    - Planned version lower than or equal to current: CRITICAL "Planned version {planned} is not higher than current {current}"
-  </action>
-</step>
-
-<step n="4" title="Completeness Verification">
-  <action>Check if the plan covers related files that would typically need updating alongside the primary changes. These are heuristic checks at WARNING level, not hard requirements:</action>
-  <action>If plan modifies a workflow, check for mentions of:
-    - workflow-manifest.csv
-    - Slash command file (.claude/commands/)
-    - checklist.md
-    - lifecycle-sequence.yaml (if the workflow has sequencing implications)
-  </action>
-  <action>If plan modifies an agent, check for mentions of:
-    - agent-manifest.csv
-    - Slash command file (.claude/commands/)
-  </action>
-  <action>If plan modifies a skill, check for mentions of:
-    - skill-registry (if applicable)
-  </action>
-  <action>For each missing related file: WARNING "Plan does not mention updating {file}"</action>
-</step>
-
-<step n="5" title="Architecture Cross-Reference">
-  <action>Check if ground truth exists at {memory_path}/validator-sidecar/ground-truth.md</action>
-  <check if="ground truth not seeded">INFO "Ground truth not available — cross-reference verification skipped". Skip remainder of this step.</check>
-  <action>If plan references ADRs (e.g., ADR-012), load the relevant ADR section from architecture.md</action>
-  <action>Verify planned changes align with ADR specifications:
-    - Components specified in the ADR are addressed by the plan
-    - Integration points mentioned in the ADR are covered
-    - Constraints from the ADR are respected
-  </action>
-  <action>For each misalignment: WARNING "Plan implements {ADR} but does not address: {component}"</action>
-</step>
-
-<step n="6" title="Classify and Present Findings">
-  <action>Load validation-patterns:severity-classification section JIT</action>
-  <action>Compile all findings from Steps 2-5 into a single list, sorted by severity (CRITICAL first, then WARNING, then INFO)</action>
-  <check if="zero findings">Present: "Plan validation complete — no findings. Plan looks clean." Then skip to Step 7 (which will write a clean validation confirmation instead of a findings table).</check>
-  <action>Present findings in a concise summary (one line per finding):
-
-  --- Validation Findings ({N}) ---
-  | # | Severity | Finding | Plan Step |
-  |---|----------|---------|-----------|
-  | 1 | CRITICAL | File `path/to/file` does not exist but plan step says "Modify" | Step 3: Detailed Edits |
-  | 2 | WARNING  | Plan does not mention updating workflow-manifest.csv | — |
-  | 3 | INFO     | Major version bump 1.29.0 → 2.0.0 — confirm intentional | Step 4: Version Bumps |
-  </action>
-  <action>Enter discussion loop:
-    - Present each finding with its number
-    - User can: [a]pprove finding, [d]ismiss finding, [e]dit finding
-    - Continue until all findings are reviewed
-    - Track which findings are approved vs dismissed
-  </action>
-  <ask>Review the findings above. For each finding, indicate [a]pprove, [d]ismiss, or [e]dit. You can also approve/dismiss all at once.</ask>
-</step>
-
-<step n="7" title="Write Plan Validation Findings">
-  <action>Load validation-patterns:findings-formatting section JIT</action>
-  <action>Collect only the APPROVED findings (exclude dismissed ones)</action>
-  <action if="findings exist">Append the approved findings to the plan artifact under a new section:
-
-  ## Plan Validation Findings
-
-  | # | Severity | Finding | Plan Step |
-  |---|----------|---------|-----------|
-  | 1 | CRITICAL | ... | ... |
-  | 2 | WARNING  | ... | ... |
-
-  **Validation date:** {date}
-  **Validator:** Val
-  **Total findings:** {approved_count} approved, {dismissed_count} dismissed
-  </action>
-  <action if="no findings (clean plan)">Append a clean validation confirmation:
-
-  ## Plan Validation Findings
-
-  No findings — plan validated clean.
-
-  **Validation date:** {date}
-  **Validator:** Val
-  </action>
-  <template-output file="{plan_artifact_path}">
-    Append Plan Validation Findings section with approved findings table, validation metadata, and summary counts.
-  </template-output>
-</step>
-<step n="8" title="Save to Val Memory">
-  <action>Auto-save all validation results to Val's memory sidecar (no user prompt required):
-
-  1. Append to {project-root}/{memory_path}/validator-sidecar/decision-log.md using standardized format:
-     ### [YYYY-MM-DD] Plan Validation: {plan_name}
-
-     - **Agent:** validator
-     - **Workflow:** val-validate-plan
-     - **Sprint:** {sprint_id or "N/A"}
-     - **Status:** recorded
-     - **Related:** {plan_artifact_path}
-
-     Validated plan: {plan_artifact_path}.
-     File targets: {file_target_count}. Version bumps: {version_bump_count}. ADR refs: {adr_count}.
-     Findings: {total_findings} ({approved_count} approved, {dismissed_count} dismissed).
-     {Brief summary of key findings}
-
-  2. Replace body of {project-root}/{memory_path}/validator-sidecar/conversation-context.md (preserve header above first ---):
-     Last session: Plan validation of {plan_name}.
-     Date: {YYYY-MM-DD}. Findings: {total_findings}.
-     Approved: {approved_count}. Dismissed: {dismissed_count}.
-
-  If {memory_path}/validator-sidecar/ directory or files don't exist, create them with standard headers:
-  decision-log.md: "# Val Validator — Decision Log\n\n> Chronological record of validation decisions.\n\n---"
-  conversation-context.md: "# Val Validator — Conversation Context\n\n> Rolling summary of the most recent validation session.\n\n---\n\nNo sessions recorded yet."
-  If writing fails, log warning and continue — memory save is non-blocking.</action>
-</step>
-</workflow>

package/_gaia/lifecycle/workflows/4-implementation/val-validate-plan/workflow.yaml

@@ -1,39 +0,0 @@
-name: val-validate-plan
-description: 'Validate implementation plan before execution — catches incorrect file targets, inconsistent version bumps, and missing scope'
-module: lifecycle
-agent: validator
-model_override: opus
-execution_mode: normal
-config_resolved: "{installed_path}/.resolved/val-validate-plan.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/4-implementation/val-validate-plan"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-required_skill_sections:
-  - "validation-patterns:claim-extraction"
-  - "validation-patterns:filesystem-verification"
-  - "validation-patterns:severity-classification"
-  - "validation-patterns:findings-formatting"
-input_file_patterns:
-  plan:
-    whole: "{plan_artifact_path}"
-    load_strategy: "FULL_LOAD"
-  architecture:
-    whole: "{planning_artifacts}/architecture.md"
-    load_strategy: "INDEX_GUIDED"
-  global_config:
-    whole: "{project-root}/_gaia/_config/global.yaml"
-    load_strategy: "FULL_LOAD"
-quality_gates:
-  pre_start:
-    - check: "plan_artifact_path is provided"
-      on_fail: "HALT: No plan artifact path specified. Usage: /gaia-val-validate-plan <path-to-plan>"
-  post_complete:
-    - check: "findings_written or clean_plan_confirmed"
-      on_fail: "HALT: Validation must complete with either written findings or explicit clean-plan confirmation. Re-run /gaia-val-validate-plan to complete validation."
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{plan_artifact_path}"

package/_gaia/lifecycle/workflows/4-implementation/validate-story/checklist.md

@@ -1,23 +0,0 @@
----
-title: 'Story Validation Check'
-validation-target: 'Story validation'
----
-## Full Validation (Step 2)
-- [ ] YAML frontmatter — all 14 required fields present and valid
-- [ ] Completeness — all template sections present
-- [ ] Clarity — ACs in Given/When/Then, subtasks linked, DoD measurable
-- [ ] Semantic quality — duplicate detection, ADR cross-references
-- [ ] Dependencies — all declared dependencies exist and resolve
-- [ ] Factual verification — claims verified against filesystem and ground truth
-## Fix Loop (Step 3)
-- [ ] SM fixes findings, Val re-validates
-- [ ] Hard limit: 3 validation attempts max
-- [ ] PASS → status set to ready-for-dev
-- [ ] FAIL after 3 → status stays validating
-## Report (Step 4)
-- [ ] Validation result appended to story file
-- [ ] Separate validation report created at story-validation-{story_key}.md
-## Val Memory (Step 5)
-- [ ] Decision-log entry auto-saved with standardized format
-- [ ] Conversation-context updated with session summary
-- [ ] Memory save is non-blocking

package/_gaia/lifecycle/workflows/4-implementation/validate-story/instructions.xml

@@ -1,146 +0,0 @@
-<workflow name="validate-story">
-<critical>
-  <mandate>Val performs full validation — completeness, clarity, semantics, dependencies, and factual verification</mandate>
-  <mandate>Append validation results to the story file</mandate>
-  <mandate>Read the story template from {project-root}/_gaia/lifecycle/templates/story-template.md for reference</mandate>
-  <mandate>Auto-save all validation results to Val memory sidecar — no user prompt required</mandate>
-</critical>
-<step n="1" title="Load Story">
-  <action if="story_key provided via arguments">Use the provided story key directly — skip the ask prompt below.</action>
-  <ask>Which story to validate? (provide story key, e.g., E1-S2)</ask>
-  <action>Find and read the story file matching {story_key}-*.md in {implementation_artifacts}/</action>
-  <action>Read the story template from {project-root}/_gaia/lifecycle/templates/story-template.md for reference</action>
-  <action>Read {planning_artifacts}/architecture.md for cross-reference validation</action>
-  <action>Read {planning_artifacts}/epics-and-stories.md for context</action>
-  <action>Read {memory_path}/validator-sidecar/ground-truth.md if it exists (for factual verification)</action>
-</step>
-<step n="2" title="Val Full Validation">
-  <action>Perform full validation on the story file:
-
-  (a) YAML Frontmatter — verify all 14 required fields present and valid:
-      key (pattern E{n}-S{n}), title (not empty), epic (valid reference),
-      status (valid state), priority (P0/P1/P2), size (S/M/L/XL),
-      points (matches sizing_map: S→2, M→5, L→8, XL→13), risk (high/medium/low),
-      sprint_id (null or valid), depends_on (list), blocks (list),
-      traces_to (list), date (valid date), author (not empty).
-      FAIL if any required field is missing or invalid.
-
-  (b) Completeness — verify all template sections present:
-      User Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Technical Notes,
-      Dependencies, Test Scenarios, Project Structure Notes, References,
-      Dev Agent Record, Estimate, Definition of Done.
-
-  (c) Clarity — check each AC is testable and in Given/When/Then format,
-      subtasks are actionable and linked to AC numbers,
-      Definition of Done items are specific and measurable.
-
-  (d) Semantic Quality — duplicate detection: load all story files for the same
-      epic, flag stories with >70% AC overlap as potential duplicates.
-      ADR cross-reference: verify each referenced ADR exists in architecture.md
-      with Accepted status. Flag Proposed/Deprecated references as warnings.
-
-  (e) Dependencies — verify all declared dependencies exist and resolve.
-
-  (f) Factual Verification — extract verifiable claims from the story
-      (file paths, component references, API endpoints, dependency versions).
-      Verify against filesystem and ground truth (if available).
-      Classify findings as CRITICAL (broken reference), WARNING (outdated), INFO (style).
-  </action>
-</step>
-<step n="3" title="Validation Fix Loop">
-  <check if="zero findings from Step 2">
-    <invoke-protocol ref="status-sync" story_key="{story_key}" new_status="ready-for-dev" source_workflow="validate-story" />
-    <action>Proceed to Step 4.</action>
-  </check>
-
-  <check if="findings exist">
-    <action>Set validation_attempt = 1.</action>
-    <invoke-protocol ref="status-sync" story_key="{story_key}" new_status="validating" source_workflow="validate-story" />
-    <action if="yolo_mode">In YOLO mode: SM auto-fixes all CRITICAL and WARNING findings without presenting to user. INFO findings are auto-acknowledged. Skip all user prompts in the fix loop.</action>
-    <action if="not yolo_mode">Present findings table to user (severity, section, claim, finding, evidence).</action>
-    <action>SM (Nate) addresses each finding:
-      - For each CRITICAL or WARNING finding: fix the story content directly
-      - For each INFO finding: fix or acknowledge with a note</action>
-    <action if="not yolo_mode">Present the corrected story sections to user for confirmation.</action>
-    <action>After SM applies all fixes, write the updated story file. Increment validation_attempt.</action>
-    <action>Re-run Val validation on the updated story (same checks as Step 2).
-      - If zero findings: invoke status-sync with new_status='ready-for-dev'. Exit loop. Proceed to Step 4.
-      - If findings remain AND validation_attempt &lt; 3: SM fixes again, Val re-validates.
-      - If findings remain AND validation_attempt = 3 (hard limit): keep status as 'validating',
-        proceed to Step 4.</action>
-  </check>
-</step>
-<step n="4" title="Save and Report">
-  <action>Append validation result at the END of the story file, after a horizontal rule (---) separator.
-    Include: date, overall PASS/FAIL verdict, validation attempts count, and per-section findings.</action>
-  <action>Create a separate validation report file at {implementation_artifacts}/story-validation-{story_key}.md with YAML frontmatter:
-    ---
-    story_key: "{story_key}"
-    validation_status: "PASS" or "FAIL"
-    validated_at: "{ISO-8601 timestamp}"
-    validation_attempts: {N}
-    findings:
-      - section: "{section name}"
-        severity: "CRITICAL" or "WARNING" or "INFO"
-        result: "PASS" or "FIXED" or "FAIL"
-        issue: "{description if FAIL or FIXED}"
-    ---
-    Then detailed findings for each section.</action>
-  <template-output file="{implementation_artifacts}/{story_key}-{story_title_slug}.md">
-    Save the story file with status updated and validation report appended.
-  </template-output>
-  <action>Display consolidated validation result DIRECTLY in the conversation:
-
-    ═══ Validation Result: {story_key} — {story_title} ═══
-
-    Status: {PASS ✓ or FAIL ✗}
-    Attempts: {validation_attempts}
-    Final status: {ready-for-dev or validating}
-
-    | # | Section | Severity | Result | Issue |
-    |---|---------|----------|--------|-------|
-    {for each finding: number, section name, CRITICAL/WARNING/INFO, PASS/FIXED/FAIL, issue description or "—"}
-
-    {if PASS:}
-    ✓ Story is ready for development.
-
-    {if FAIL:}
-    ✗ {remaining_count} findings unresolved after {validation_attempts} attempts.
-    Run /gaia-fix-story {story_key} to address remaining issues.
-
-    Files updated:
-    - {implementation_artifacts}/{story_key}-*.md (status + validation appended)
-    - {implementation_artifacts}/story-validation-{story_key}.md (standalone report)</action>
-</step>
-<step n="5" title="Save to Val Memory">
-  <action>Auto-save all validation results to Val's memory sidecar (no user prompt required):
-
-  1. Append to {memory_path}/validator-sidecar/decision-log.md using standardized format:
-     ### [YYYY-MM-DD] Story Validation: {story_key}
-
-     - **Agent:** validator
-     - **Workflow:** validate-story
-     - **Sprint:** {sprint_id or "N/A"}
-     - **Status:** recorded
-     - **Related:** {story_key}
-
-     Validated story {story_key} ({story_title}).
-     Result: {PASS or FAIL after N attempts}.
-     Findings: {total_count} total, {fixed_count} fixed, {remaining_count} remaining.
-     Final status: {ready-for-dev or validating}.
-     {Brief summary of key findings and fixes}
-
-  2. Replace body of {memory_path}/validator-sidecar/conversation-context.md (preserve header above first ---):
-     Last session: Story validation of {story_key} ({story_title}).
-     Date: {YYYY-MM-DD}. Result: {PASS/FAIL}. Attempts: {N}.
-     Findings: {count}. Fixed: {fixed_count}.
-
-  If {memory_path}/validator-sidecar/ directory or files don't exist, create them with standard headers.
-  If writing fails, log warning and continue — memory save is non-blocking.</action>
-</step>
-<next-step source="lifecycle-sequence.yaml">
-  <on_pass command="/gaia-create-story">Create more stories, or run /gaia-sprint-plan when all stories are ready</on_pass>
-  <on_fail command="/gaia-fix-story">Fix validation failures, then re-validate</on_fail>
-  <alternative command="/gaia-sprint-plan" context="When all stories are created and validated (ready-for-dev)"/>
-</next-step>
-</workflow>

package/_gaia/lifecycle/workflows/4-implementation/validate-story/workflow.yaml

@@ -1,25 +0,0 @@
-name: validate-story
-description: 'Full story validation — completeness, clarity, and factual verification'
-module: lifecycle
-agent: validator
-template_output_prompt: "auto"
-config_resolved: "{installed_path}/.resolved/validate-story.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/4-implementation/validate-story"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-input_file_patterns:
-  architecture:
-    whole: "{planning_artifacts}/architecture.md"
-    load_strategy: "INDEX_GUIDED"
-  epics:
-    whole: "{planning_artifacts}/epics-and-stories.md"
-    load_strategy: "INDEX_GUIDED"
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{implementation_artifacts}/{story_key}-{story_title_slug}.md"
-  secondary: "{implementation_artifacts}/sprint-status.yaml"
-  validation_report: "{implementation_artifacts}/story-validation-{story_key}.md"

package/_gaia/lifecycle/workflows/5-deployment/deployment-checklist/checklist.md

@@ -1,29 +0,0 @@
----
-title: 'Deployment Checklist Validation'
-validation-target: 'Deployment checklist'
-required-inputs:
-  - '{test_artifacts}/traceability-matrix.md'
-  - '{test_artifacts}/ci-setup.md'
-  - '{planning_artifacts}/readiness-report.md'
----
-## Pre-Deployment
-- [ ] DB migrations verified
-- [ ] Feature flags configured
-- [ ] Config changes applied
-## Dependencies
-- [ ] External services verified
-- [ ] API compatibility confirmed
-## Test Infrastructure (HALT if missing)
-- [ ] traceability-matrix.md exists at {test_artifacts}/traceability-matrix.md
-- [ ] ci-setup.md exists at {test_artifacts}/ci-setup.md with enforced quality gates
-- [ ] readiness-report.md status is PASS
-## Rollback
-- [ ] Rollback plan exists
-- [ ] Rollback tested in staging
-## Approvals (HALT if not CONFIRMED)
-- [ ] QA sign-off: CONFIRMED (all tests passing, no critical bugs)
-- [ ] Security sign-off: CONFIRMED (review complete, no critical findings)
-- [ ] Stakeholder approval: CONFIRMED
-- [ ] Go/no-go recommendation provided
-## Output Verification
-- [ ] Checklist file generated

package/_gaia/lifecycle/workflows/5-deployment/deployment-checklist/instructions.xml

@@ -1,59 +0,0 @@
-<workflow name="deployment-checklist">
-<critical>
-  <mandate>Every deployment must have a verified rollback plan</mandate>
-  <mandate>All approval gates must be explicitly confirmed</mandate>
-  <mandate>Never deploy without pre-deployment checks passing</mandate>
-</critical>
-<step n="1" title="Load Deployment Context">
-  <action>Read {planning_artifacts}/architecture.md — understand system components</action>
-  <action>Read {planning_artifacts}/infrastructure-design.md if available</action>
-  <action>Read {test_artifacts}/traceability-matrix.md — verify requirement coverage</action>
-  <action>Read {test_artifacts}/ci-setup.md — verify CI quality gates</action>
-  <action>Read {planning_artifacts}/readiness-report.md — verify PASS status</action>
-  <action>Identify release scope: what stories, features, fixes are included</action>
-</step>
-<step n="2" title="Optional: Accessibility Testing">
-  <ask>Would you like to create an accessibility test plan? This spawns a subagent in a separate context. Recommended for frontend/user-facing applications. (yes / skip)</ask>
-  <action>If yes: spawn a subagent using the Agent tool: "Load {project-root}/_gaia/core/engine/workflow.xml, then process {project-root}/_gaia/testing/workflows/accessibility-testing/workflow.yaml as workflow-config. Run in YOLO mode. Follow the workflow engine instructions EXACTLY."</action>
-  <action>If skip: accessibility testing can be set up anytime later with /gaia-a11y-testing</action>
-</step>
-<step n="3" title="Pre-Deployment Checks">
-  <action>Verify DB migrations are tested and reversible</action>
-  <action>Confirm feature flags are configured correctly</action>
-  <action>Check configuration changes are applied to target environment</action>
-  <action>Verify secrets rotation is complete if required</action>
-</step>
-<step n="4" title="Dependency Verification">
-  <action>Confirm external service availability (APIs, databases, caches)</action>
-  <action>Verify API compatibility with consumers</action>
-  <action>Check third-party service SLAs and maintenance windows</action>
-</step>
-<step n="5" title="Rollback Readiness">
-  <action>Verify rollback plan exists and is documented</action>
-  <action>Confirm rollback has been tested in staging</action>
-  <action>Verify DB migration rollback scripts work</action>
-  <action>Define rollback trigger criteria</action>
-</step>
-<step n="6a" title="Automated Verification Gates">
-  <action>Verify readiness-report.md status is PASS — if not PASS, HALT deployment</action>
-  <action>Verify traceability-matrix.md coverage is complete — flag gaps as blocking</action>
-  <action>Verify ci-setup.md quality gates are enforced (not advisory-only)</action>
-</step>
-<step n="6b" title="QA Sign-Off">
-  <ask>QA sign-off: confirm all acceptance tests pass and no critical bugs are open. Enter CONFIRMED or provide blocking issue.</ask>
-  <check if="qa_signoff != CONFIRMED">HALT: QA sign-off is required before deployment. Resolve the blocking issue and re-run.</check>
-</step>
-<step n="6c" title="Security Sign-Off">
-  <ask>Security sign-off: confirm security review is complete with no critical findings. Enter CONFIRMED or provide blocking findings.</ask>
-  <check if="security_signoff != CONFIRMED">HALT: Security sign-off is required before deployment. Resolve blocking findings and re-run.</check>
-</step>
-<step n="6d" title="Stakeholder Approval">
-  <ask>Stakeholder approval: confirm release scope is approved. Enter CONFIRMED.</ask>
-  <check if="stakeholder_approval != CONFIRMED">HALT: Stakeholder approval required before deployment.</check>
-</step>
-<step n="7" title="Generate Checklist">
-  <template-output file="{implementation_artifacts}/deployment-checklist-{date}.md">
-    Generate deployment checklist with: pre-deployment checks, dependency status, rollback readiness, approval gates, go/no-go recommendation.
-  </template-output>
-</step>
-</workflow>

package/_gaia/lifecycle/workflows/5-deployment/deployment-checklist/workflow.yaml

@@ -1,39 +0,0 @@
-name: deployment-checklist
-description: 'Pre-deployment verification checklist'
-module: lifecycle
-agent: devops
-config_resolved: "{installed_path}/.resolved/deployment-checklist.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/5-deployment/deployment-checklist"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-input_file_patterns:
-  architecture:
-    whole: "{planning_artifacts}/architecture.md"
-    load_strategy: "FULL_LOAD"
-  infrastructure:
-    whole: "{planning_artifacts}/infrastructure-design.md"
-    load_strategy: "FULL_LOAD"
-  traceability:
-    whole: "{test_artifacts}/traceability-matrix.md"
-    load_strategy: "FULL_LOAD"
-  ci_setup:
-    whole: "{test_artifacts}/ci-setup.md"
-    load_strategy: "FULL_LOAD"
-  readiness_report:
-    whole: "{planning_artifacts}/readiness-report.md"
-    load_strategy: "FULL_LOAD"
-quality_gates:
-  pre_start:
-    - check: "traceability_exists"
-      on_fail: "HALT: Run /gaia-trace before deployment."
-    - check: "ci_setup_exists"
-      on_fail: "HALT: Run /gaia-ci-setup before deployment."
-    - check: "readiness_passed"
-      on_fail: "HALT: Readiness report must show PASS. Run /gaia-readiness-check."
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{implementation_artifacts}/deployment-checklist-{date}.md"

package/_gaia/lifecycle/workflows/5-deployment/post-deploy-verify/checklist.md

@@ -1,19 +0,0 @@
----
-title: 'Post-Deploy Verification'
-validation-target: 'Post-deployment report'
-required-inputs: []
----
-## Health
-- [ ] Health endpoints responding
-- [ ] Service connectivity confirmed
-## Smoke Tests
-- [ ] Critical paths validated
-- [ ] API endpoints verified
-## Metrics
-- [ ] Error rate within SLO
-- [ ] Latency within bounds
-- [ ] Throughput at expected levels
-## Status
-- [ ] Overall deployment status declared
-## Output Verification
-- [ ] Post-deploy report generated

package/_gaia/lifecycle/workflows/5-deployment/post-deploy-verify/instructions.xml

@@ -1,33 +0,0 @@
-<workflow name="post-deploy-verify">
-<critical>
-  <mandate>Health checks must pass before declaring deployment successful</mandate>
-  <mandate>Metrics must be within SLO bounds</mandate>
-  <mandate>Trigger rollback if any critical check fails</mandate>
-</critical>
-<step n="1" title="Health Checks">
-  <action>Verify application health endpoints respond correctly</action>
-  <action>Confirm service connectivity: databases, caches, queues, external APIs</action>
-  <action>Check all containers/instances are running and healthy</action>
-</step>
-<step n="2" title="Smoke Tests">
-  <action>Execute critical path validation: login, core feature, key user journeys</action>
-  <action>Verify API endpoints return expected responses</action>
-  <action>Check static assets and CDN serving correctly</action>
-</step>
-<step n="3" title="Metric Validation">
-  <action>Check error rate is within SLO bounds</action>
-  <action>Verify latency (P50, P95, P99) within acceptable range</action>
-  <action>Confirm throughput matches expected levels</action>
-  <action>Monitor resource utilization: CPU, memory, disk</action>
-</step>
-<step n="4" title="Canary Analysis">
-  <action>If canary deployment: compare canary vs baseline metrics</action>
-  <action>Evaluate statistical significance of metric differences</action>
-  <action>Recommend: proceed, hold, or rollback</action>
-</step>
-<step n="5" title="Generate Report">
-  <template-output file="{implementation_artifacts}/post-deploy-{date}.md">
-    Generate post-deployment report with: health check results, smoke test results, metric comparison, canary analysis (if applicable), overall deployment status.
-  </template-output>
-</step>
-</workflow>

package/_gaia/lifecycle/workflows/5-deployment/post-deploy-verify/workflow.yaml

@@ -1,15 +0,0 @@
-name: post-deploy-verify
-description: 'Post-deployment health and metric validation'
-module: lifecycle
-agent: devops
-config_resolved: "{installed_path}/.resolved/post-deploy-verify.yaml"
-config_source: "{project-root}/_gaia/lifecycle/config.yaml"
-installed_path: "{project-root}/_gaia/lifecycle/workflows/5-deployment/post-deploy-verify"
-instructions: "{installed_path}/instructions.xml"
-validation: "{installed_path}/checklist.md"
-on_error:
-  missing_file: "ask_user"
-  unresolved_variable: "halt"
-
-output:
-  primary: "{implementation_artifacts}/post-deploy-{date}.md"

package/_gaia/lifecycle/workflows/5-deployment/release-plan/checklist.md

@@ -1,20 +0,0 @@
----
-title: 'Release Plan Validation'
-validation-target: 'Release plan document'
-required-inputs: []
----
-## Scope
-- [ ] Release contents listed (stories, fixes, breaking changes)
-- [ ] Version number assigned
-## Strategy
-- [ ] Deployment strategy selected with rationale
-- [ ] Success criteria defined
-## Rollout
-- [ ] Staged percentages defined
-- [ ] Observation windows set
-- [ ] Abort criteria specified
-## Communication
-- [ ] Stakeholder notification planned
-- [ ] Changelog prepared
-## Output Verification
-- [ ] Release plan file generated