dhpk-opsx-load-contextlisted

# opsx-load-context Context loading skill for `opsx-apply-resume` Resume Phase. Implements a 3-tier fallback so that context is always available even if earlier tiers fail. ## When NOT to Use - Saving / posting a session observation → use `dhpk-opsx-post-observation` - Generating a `/goal` condition for a fresh session → use `dhpk-opsx-apply-goal` - Any phase other than `opsx-apply-resume` Resume Phase (Steps 1b–1d) ## Inputs | Variable | Source | Description | |----------|--------|-------------| | `claude_mem_obs_id` | Handoff frontmatter | Integer obs ID, or null / absent | | `compact_json_path` | Handoff frontmatter | Relative path like `compact-notes/compact-*.json`, or absent | | `next_action_hint` | First Next Action from handoff | Key terms for cross-session search; may be empty | ## Fallback Chain Work through tiers in order. Stop at the first successful tier and record `CONTEXT_SOURCE`. --- ### Pre-chain — Hard-rule escalation (highest priority — blocking human decision) **Condition**: An active change carries a `.hard-rule-escalation.md` written by `dhpk-opsx-apply-goal` because unattended implementation hit an explicit hard-rule conflict that could not be resolved without human input. Check this before routine carry-forward such as `.resume-note.md`. ```bash ESCALATION=$(ls -t openspec/changes/*/.hard-rule-escalation.md 2>/dev/null | head -1) ``` - File found → read it and surface it as a blocking human decision. Set `CONTEXT_SOURCE = ".hard-rule-esca