Packwright 0.1.2

Packwright 0.1.2 closes the local runtime-automation loop across Codex, Claude
Code, and Cursor while keeping canonical intent separate from task handoff and
portable instance state.

Canonical local automations

• Runtime-neutral mechanism 0.8 declares bounded session_start and
  user_prompt context automations.
• Declarative producers cover local memory views, current date/time facts, and
  target relocation checks. They do not trigger from prompt keywords and do not
  run arbitrary user commands.
• Legacy mechanism 0.5, 0.6, and 0.7 sources normalize in memory to the 0.8
  contract without rewriting editable source files.

Native runtime projection

• Claude Code receives project-local SessionStart and UserPromptSubmit
  command hooks.
• Codex receives project-local SessionStart and UserPromptSubmit hooks and
  records project trust/hook review as an activation step.
• Cursor receives sessionStart context. Its beforeSubmitPrompt surface
  cannot add model context, so Packwright records
  unavailable_missing_effect instead of claiming compatibility.
• Generated Python runners enforce UTF-8 byte budgets and read only local
  project files. Cloud agents remain outside this release scope.

Reconcile and ownership

• packwright reconcile previews and applies same-instance mechanism upgrades
  from canonical intent rather than reverse-compiling another runtime's hooks.
• Plans and receipts include installed/desired spec hashes, optional Git
  provenance, managed projection changes, preserved instance state, manual
  merges, capability gaps, and pending activation steps.
• Runtime JSON uses entry-level Packwright ownership and fragment hashes.
  Install, reconcile, and doctor preserve unrelated user settings and hooks.
• Existing installed Emotion Engine sidecars and live portable state survive
  reconcile.

Adoption and migration safety

• Adopt classifies existing local hooks as automation candidates and can create
  evidence-only canonicalization drafts. It never reverse-compiles behavior or
  edits mechanism.yaml automatically.
• Migration inventories unmanaged hook configuration and supporting assets,
  reports destination behavior gaps, and requires separate
  --accept-degraded confirmation before non-interactive apply.
• Handoff remains task continuity only. It does not transfer hooks, skills,
  schemas, or memory structure.

Install

python -m pip install packwright==0.1.2
packwright --version

Then follow the README quickstart, use the
paste-ready coding-agent prompt, or read the
local runtime automation contract.

Verification

The local release gate passes 96 tests, Python compilation, zero-network audit,
public-tree history audit, generated runner execution for all three adapters,
Claude Code/Codex prompt-refresh execution, Cursor capability degradation,
state-preserving reconcile, and evidence-only adoption drafts.

Packwright 0.1.2 remains local-only. It does not add cloud hook execution,
scheduled tasks, session_end, pre_compact, or arbitrary custom commands.