Skip to content

Packwright 0.3.0 — Pi Core support

Choose a tag to compare

View all tags
@pioneerjeff pioneerjeff released this 24 Jul 15:17
v0.3.0
2ef5e32

Packwright 0.3.0 adds first-class Pi Core support and makes its verification language more honest. One canonical agent source can now build native targets for Pi, Codex, Claude Code, and Cursor, with all 12 directed migration paths covered by the release gate.

Install

python -m pip install packwright==0.3.0

Pi Core

Build and install a native Pi target:

packwright init --template code --name Nova -o work/nova
packwright build work/nova --adapter pi -o pack/nova-pi
packwright install pack/nova-pi --adapter pi --target project/nova-pi

The Pi adapter emits:

  • AGENTS.md for project context;
  • .agents/skills/<name>/SKILL.md for project Agent Skills;
  • .pi/<name>/references/ for adapter-scoped references; and
  • explicit project-trust activation guidance for /trust or pi --approve.

Packwright does not generate executable Pi extensions. Canonical session_start and user_prompt automations are recorded as capability gaps, and migration to Pi requires --accept-degraded after review. Pi Core also has no built-in MCP surface, so the optional Emotion Engine runtime cannot be activated there; portable state may still be carried as inert data.

Honest readiness

score continues to provide the stable structural passed result, but now includes a machine-readable packwright-readiness/v1 block. A structural 100.0 explicitly leaves portable state, runtime activation, environment bindings, and workflow acceptance as not_evaluated.

doctor keeps its backward-compatible ok result for managed projection integrity and adds target readiness evidence. It reports:

  • unverified Pi project trust;
  • unavailable or review-pending canonical automations;
  • pending adoption-review items; and
  • the readiness layers that Packwright cannot yet evaluate.

This is intentionally a minimal false-green fix: existing automation can keep using passed and ok, while people and newer integrations can stop treating structural integrity as proof of live workflow readiness.

Other hardening

  • install --dry-run returns a complete no-write change plan.
  • Install provenance is persisted under .packwright/install-provenance.json and exposed by doctor.
  • Legacy Emotion Engine state can be explicitly retired as a verified backup.
  • Reconcile now converges against the same final projection used for scoring, installation, and artifact locking.

Compatibility

Packwright 0.3.0 remains local-only and requires Python 3.9 or newer. Existing 0.2.0 canonical sources and installed targets remain diagnosable, migratable, and reconcilable. Installing the Python package alone does not modify a target.

Assets 2
Loading