# Canonical manifest template for /hotfix command.
# Source of truth for manifest schema — do not duplicate elsewhere.
# Placeholders: {name}, {description}, {date}
# Written to: .forge/work/hotfix/{name}/manifest.yaml
#
# Hotfix uses a compressed phase set — see quality-gates.md "Hotfix Gate
# Exemptions" for rationale. Follow-up work is tracked in an associated
# gotcha file with the `hotfix-workaround` tag.

schema_version: "6"
name: {name}
type: hotfix
description: "{description}"
status: in-progress  # in-progress | paused | completed | escalated
created: "{date}"
command: hotfix
escalated_from: null
successor_path: null  # filled when follow-up /bugfix or /feature is created

# Hotfix workflow is intentionally compressed — full /bugfix scrutiny happens
# in the follow-up ticket. active-light values are common here. Allowed
# values: active | active-light | active-commit-only | skipped | as-discovered
# | complete-inline.
phase_plan:
  debug-root-cause: active
  production-build: active
  smoke-tests: active
  code-review-critical: active
  deliver: active
  gotchas: as-discovered
  followup-ticket: as-discovered

# Gate state. No slice_graph — hotfixes are by definition too urgent to plan
# a decomposition.
phases:
  debug:
    root-cause: { status: pending, gate-passed: false }
  quality:
    smoke-tests: { status: pending, gate-passed: false }
    code-review-critical: { status: pending, gate-passed: false }
  deliver:
    deployed: false
  support:
    gotchas-recorded: false
    followup-ticket: null  # e.g. work/bugfix/payment-null-check-proper-fix