00013test-layout-completeAPG-TEST0 authorized a bounded repository test-ownership change. The phase
establishes the src/test/unit/<language> and src/test/int/<language>
convention, adds behavior-focused Bats tests for both APG report commands, and
migrates the existing project-skill Python suite into the integration layout.
The accepted report formats, command interfaces, shared helper behavior, project-skill behavior, skill content, maturity model, dependency model, and publication boundary remain unchanged.
The repository now owns:
src/test/unit/bash/git-show-report.unit.test.bats;src/test/unit/bash/append-operational-report.unit.test.bats; andsrc/test/int/python/apg_project_skills.int.test.py.The Bats suites cover 22 behavior families across exact record construction, hash and framing boundaries, input validation, Git commit forms, path handling, private permissions, unsafe destinations, failure atomicity, concurrent appends, duplicate records, and multi-project concatenation. Their expectations use the canonical Agent report envelope and shared helper.
The migrated Python suite preserves all 28 project-skill integration families. Only its repository-root resolution and path changed.
The README records the test-level directories, filename suffixes, framework requirements, and direct suite commands. The APG7A provenance destination now points to the migrated integration test. Historical exit records remain unchanged.
No package manager, dependency manifest, generalized test runner, or coverage gate was introduced.
planning-repository-work applied to the dependent inventory, baseline,
migration, test-porting, documentation, verification, and publication units.implementing-with-test-discipline applied because the phase adds executable
regression evidence and changes test discovery paths.reviewing-and-verifying-repository-work applied to the complete resulting
state and terminal claims.designing-significant-changes was a material non-trigger because the
maintainer supplied the test layout, ownership transfer, and phase identity.debugging-systematically was a material non-trigger because baseline and
migrated suites exposed no unexplained failure.composing-bounded-worker-assignments was a non-trigger because no internal
delegation was authorized or used.No Superpowers skill was invoked or followed.
Fresh validation from the resulting repository state established:
00013; andThe phase changes no report implementation or project-skill implementation, so no executable behavior delta required a source correction.
APG-TEST0 is complete after one APG commit and push. It authorizes no report format or implementation change, dependency manifest, test-runner abstraction, coverage gate, workflow-skill maturity change, publication, release, or successor phase automatically.