Update to Hypertaks

{
  "description": "Create and resume verified project checkpoints, produce safe cross-agent handoffs, reconcile work with Git and acceptance criteria, and reject unsupported completion claims.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 282
    }
  ],
  "name": "hypertaks-continuity",
  "skill_md_contents": "---\nname: hypertaks-continuity\ndescription: \"Create and resume verified project checkpoints, produce safe cross-agent handoffs, reconcile work with Git and acceptance criteria, and reject unsupported completion claims.\"\n---\n\n# Hypertaks Continuity\n\nUse this skill for pausing, resuming, handing off, reconciling, or proving completion of a meaningful Hypertaks task.\n\nLoad `../hypertaks/references/00-security-kernel.md` first. Continuity artifacts preserve scope and evidence. They do not create new permission, approval, or authority.\n\n## Public actions\n\n- `checkpoint`: capture the active objective, contract, actual repository identity, branch, commit, changed files, completed work, pending work, blockers, next action, permissions, test evidence, and acceptance criteria.\n- `resume`: read the checkpoint and compare it with actual Git state. Refuse silent continuation on a repository, branch, or commit mismatch.\n- `handoff`: produce a compact cross-agent document without copying the raw transcript or secrets.\n- `reconcile`: compare the approved contract, expected artifacts, working tree, tests, and open criteria.\n- `status`: report active checkpoint state and stale evidence.\n- `proof-of-done`: return `DONE` only when current evidence proves every required criterion. Otherwise return `NOT_DONE` with exact reasons.\n\n## Checkpoint evidence\n\nRead branch and commit from Git. Never default to `main`, `head`, wildcard values, or caller assertions. Test evidence records the command, exit code, timestamp, and tested commit. Acceptance criteria carry an identifier, status, and evidence locator.\n\nA checkpoint with missing tests, stale test evidence, pending work, blockers, failed criteria, or a commit mismatch cannot pass proof of done.\n\n## Storage safety\n\nWrite only inside an approved project or brain root. Validate checkpoint identifiers, use atomic writes, and scan the entire serialized artifact for secrets before persistence. Handoffs must redact secret-like values while preserving the existence of the redaction.\n\nDo not checkpoint harmless Nano answers. Suggest a checkpoint at a meaningful pause, host session end, or handoff boundary when the configured policy allows it.\n\nReturn actual Git state, checkpoint ID, completed and open criteria, evidence status, exact next action, and the final `DONE` or `NOT_DONE` verdict.\n"
}