APG v0.2.0
APG v0.2.0 — Stable Core and Reproducible Delivery
APG v0.2.0 turns the initial six-skill foundation into a stable, mechanically validated release and lifecycle system.
The release preserves the focused process model introduced in v0.1.0 while substantially strengthening maturity evidence, public distribution, installation safety, regression coverage, and long-term maintainability.
Highlights
All six process skills are now stable
Following repeated real-project use, representative non-triggers, edge and stop behavior, complete regression testing, post-Superpowers evidence, and fresh non-author review, all six original skills are promoted to stable:
composing-bounded-worker-assignmentsdesigning-significant-changesplanning-repository-workimplementing-with-test-disciplinedebugging-systematicallyreviewing-and-verifying-repository-work
Stable means suitable for routine bounded use within each documented trigger and project-owned authority boundary. It does not mean universal applicability, automatic invocation, production warranty, or comparative superiority.
Focused implementation-discipline correction
implementing-with-test-discipline now accounts for locally owned code or test artifacts whose sole purpose ends because of an authorized change—when removal policy and authority are clear.
This is a narrow consistency rule, not permission for unrelated cleanup or independently owned lifecycle decisions.
Reproducible public releases
The new apg-public-release command builds and validates deterministic public candidates with:
- exact non-private source projection;
- byte- and mode-preserving path equality;
- one-parent append-only release history;
- annotated version tags;
- reproducible manifests, trees, commits, and tag objects;
- critical-owner and wrapper checks;
- licensing and confidentiality validation; and
- configured unit and integration tests.
The release process now detects the omitted-wrapper defect present in public v0.1.0.
Managed user-scoped lifecycle
The new apg-user-skills command supports:
listinstalladoptcheckupdaterollbackuninstall
It uses direct skill links, strict source identity validation, state-last updates, persistent locking, exact ownership records, and conservative rollback. Unrelated user skills and unowned containers remain outside its authority.
Mechanical skill-library validation
apg-check-skill-library provides a dependency-free, read-only checker for the adopted mechanical skill contract, including canonical leaves, catalog consistency, link containment, and checked-in discovery projection.
A passing check establishes mechanical consistency—not semantic usefulness, maturity, privacy, provenance sufficiency, or runtime discovery.
Distribution and testing improvements
v0.2.0 also:
- restores the missing
bin/apg-project-skillswrapper; - establishes an exact public-surface policy;
- separates unit and integration test layouts;
- strengthens public lineage and read-only validation;
- formalizes skill authoring, correction, maturity, deprecation, and removal;
- closes the legacy candidate-theme queue with explicit dispositions; and
- preserves v0.1.0 as the immutable root of the public release chain.
Superpowers is retired from the maintainer workflow. A subsequent fresh RepoMap session discovered all six public skills, applied the review skill successfully, passed managed checks, and preserved the target repository.
Upgrading from v0.1.0
Upgrading is strongly recommended because v0.2.0 restores the missing project-local wrapper and introduces strict release, installation, update, and rollback validation.
For a managed user-scoped installation from an exact public checkout:
bin/apg-user-skills install --source <v0.2.0-public-checkout>
bin/apg-user-skills checkFor project-local installation:
bin/apg-project-skills install --repo <target-repository>
bin/apg-project-skills check --repo <target-repository>A full Codex restart may be necessary when newly linked skills do not appear immediately.