Packwright 0.1.1

Packwright 0.1.1

Packwright 0.1.1 hardens portability across Codex, Claude Code, and Cursor while
keeping the compiler deterministic, local, and inspectable.

Runtime-neutral foundations

• Adapter names, native paths, guidance formats, capabilities, and lifecycle
  behavior now live in a central registry instead of leaking through canonical
  character and skill specifications.
• Install infers the adapter from the pack manifest; --adapter remains an
  optional assertion.
• Existing 0.1.0 mechanism and installed-target metadata is normalized into the
  current runtime-neutral contract for diagnosis, scoring, and migration.

Emotion Engine v1.0.0

• The optional Emotion Engine integration is now adapter-neutral and available
  to Codex, Claude Code, and Cursor.
• Each adapter receives its native guidance and project MCP configuration while
  sharing the same pinned v1.0.0 runtime and canonical
  .emotion-engine/state.json state file.
• Legacy state files are carried byte-for-byte when unambiguous. Conflicting
  legacy states stop before target writes, and refresh, doctor, and force flows
  do not reset live state.

Skills and locale

• Every semantic skills: entry projects through the adapter registry.
  Capability requirements can degrade explicitly without putting runtime names
  in the canonical mechanism.
• Compiler-owned boilerplate supports deterministic en and zh-CN output.
  Missing or unsupported locales fall back to English, while user-authored
  identity, memory, and skill prose remains unchanged.
• Checker rules use resolved locale and semantic section contracts instead of
  relying on English-only headings.

Safer shorter workflows

• packwright new can create source, build a checked pack, and install a fresh
  target in one command while preserving all three directories. It refuses
  existing or overlapping paths.
• Preset use through new requires explicit --accept-preset after review.
• Reviewed adoption queues now have a dry-run-first apply phase with per-item
  SHA-256 checks. Safe workspace/skill copies and source registrations can be
  applied; memory merge and knowledge promotion remain manual.
• Agent-operation documentation now identifies which safeguards are enforced
  mechanically and which depend on the coding agent following the prompt.
• Installed handoff wrappers use the scoped PACKWRIGHT_PYTHON override rather
  than inheriting a build environment's generic PYTHON path.

Install

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

Then follow the README quickstart or use the
paste-ready coding-agent prompt.

Verification

The release gate runs the complete source suite across Python 3.9 through 3.14,
zero-network and public-tree audits, wheel and sdist validation, clean package
installs, all three adapter workflows, and migration integrity checks.

As before, a 100.0 score proves the structural contract passes; it is not a
guarantee of runtime behavior. Packwright itself makes no network requests and
sends no telemetry.