v0.1.10

v0.1.10 — Protected publication rollout

This release verifies Packy's protected publication path after the repository
governance rollout. It does not introduce new Packy CLI behavior or change the
documented install, update, or uninstall workflows.

Repository controls

• Packy's required checks now protect main through the reviewed pull-request
  path, with force pushes and branch deletion denied.
• Release and Homebrew authority remain separated behind their protected
  environments. The tap credential exists only in the homebrew environment;
  there is no repository-level fallback credential.
• Version tags are protected from routine movement and deletion, and this is
  the first Packy version published after future-release immutability is
  enabled.

Publication integrity

• The release is built once from one exact protected-main commit and carries
  deterministic SHA-256 checksums, an SPDX SBOM, and verified provenance.
• GitHub publication completes and is independently read back before the
  separately approved Homebrew update can begin.
• Published release assets and the associated version tag are immutable. Normal
  correction uses a new monotonically increasing version. Release title and
  notes remain editable residual Owner authority; destructive release deletion
  is an Owner-only break-glass action and permanently prevents reuse of the
  deleted version tag.

Operator impact and limitations

• Claude Code stable 2.1.203 or newer remains the supported floor, and
  existing installations remain on state schema v2.
• matty 3.0.0 has a complete Claude Code contract.
• engram 2.0.0 remains degraded on Claude Code where generic lifecycle
  translation is unsupported.
• No Packy-managed files or state schemas change in this release.
• Existing installations continue to use brew upgrade packy, followed by
  packy init, packy update --dry-run, and packy update.
• Packy remains macOS-first. Darwin Homebrew installs are the supported user
  path; Linux artifacts remain published for future support.

v0.1.9

v0.1.9 — First-class Claude Code support

This is the first Packy release with Claude Code as a supported global surface
alongside Codex and OpenCode.

Operator changes

• Claude Code is a user-managed prerequisite. Install stable Claude Code
  2.1.203 or newer before applying Packy; Packy does not install, upgrade,
  authenticate, or run a model.
• Classic state migrates from v1 to state schema v2 only after a verified
  Apply. Existing Codex/OpenCode ownership is preserved while Claude becomes a
  desired surface.
• Existing unmanaged, ambiguous, or drifted Claude files, instructions, hooks,
  skills, agents, and user MCP definitions are preserved for explicit recovery.

Capability packs

• matty 3.0.0 has a complete Claude Code contract.
• engram 2.0.0 is activatable but degraded on Claude Code: instructions
  and the exact user MCP projection are native, while generic Engram lifecycle
  translation remains an optional generic-lifecycle-unsupported exclusion.

Limitations

• Packy does not use Claude plugins, project/local Claude configuration, managed
  policy, credentials, login, authentication, REPL, print/model mode, or model
  calls.
• Packy does not claim Claude usability from a successful Apply. Check fresh
  readiness and complete any host-owned trust, reload, or runtime steps.
• Packy remains macOS-first. Artifact names, supported platform artifacts,
  checksums, Homebrew dependencies, and the formula's packy --version test are
  unchanged.

v0.1.7

What's Changed

• Harden Matty-owned validation against vendored upstream discovery by @yersonargotev in #39
• Introduce source configuration and deterministic read-only Check by @yersonargotev in #40
• Preserve immutable matty 1.0.0 history by @yersonargotev in #41
• Move upstream adaptations to a Matty-owned seam by @yersonargotev in #42
• Deliver transactional Apply, Recover, and truthful initial provenance by @yersonargotev in #43
• Orchestrate fail-closed classification without publication by @yersonargotev in #44
• Deliver manual-first pack synchronization workflow by @yersonargotev in #45
• feat: deliver sync-pack-source maintainer skill by @yersonargotev in #46
• Fix GitHub API 403 classification in pack-source Inspect by @yersonargotev in #48
• Cut over the atomic Packy product identity by @yersonargotev in #67

Full Changelog: v0.1.6...v0.1.7

Platform support

Packy v0 is macOS-first: macOS is the supported v0 path. Linux artifacts are published for future support and are not part of the current v0 golden path.

v0.1.6

What's Changed

• Fix annotated-tag test Git identity isolation by @yersonargotev in #20

Full Changelog: v0.1.5...v0.1.6

Platform support

Matty v0 is macOS-first. Darwin Homebrew installs are the supported user path. Linux artifacts are published for future support and are not part of the current golden path.

v0.1.5

What's Changed

• Fix init release tag retention in Installed Source by @yersonargotev in #18

Full Changelog: v0.1.4...v0.1.5

Platform support

Matty v0 is macOS-first. Linux artifacts are published for future support, but Linux is not part of the current golden path.

v0.1.4

What's Changed

• chore: remove external reference trees by @yersonargotev in #15
• feat: show init clone progress by @yersonargotev in #16

Full Changelog: v0.1.3...v0.1.4

v0.1.3

What's Changed

• feat: show skill source origin by @yersonargotev in #9
• feat: audit Engram doctor resolution by @yersonargotev in #10
• feat: warn about unmanaged skill symlink recovery by @yersonargotev in #11
• feat: diagnose engram ownership by @yersonargotev in #12

Full Changelog: v0.1.2...v0.1.3

v0.1.2

What's Changed

• feat: add Matty-managed rules prompt block by @yersonargotev in #8

Full Changelog: v0.1.1...v0.1.2

v0.1.1

What's Changed

• chore: update skills bundle to v1.1 by @yersonargotev in #2

New Contributors

• @yersonargotev made their first contribution in #2

Full Changelog: v0.1.0...v0.1.1

v0.1.0

Full Changelog: https://github.com/yersonargotev/matty/commits/v0.1.0