…0 fresh from main (#118)

## Why (five-whys)

**Symptom**: M131's "merge aprender#1078" path failed — workspace-test reproducibly broken on the rebased branch. Operator selected path 2 (close + author fresh).

**Why-1**: PR #1078's failure was reproducible on rerun — not a flaky test.
**Why-2**: Failure specific to #1078's 22 ahead-of-main commits interacting with current main's auto_memory test.
**Why-3**: Investigating that interaction is substantial work unrelated to the contract bump.
**Why-4**: Closing #1078 + authoring fresh from main is structurally cleaner — removes the "PR-pinned canonical" anomaly M130 identified.
**Why-5**: **Root cause**: the M0 mirror PR was a holdover from a different era; v1.24.0 is the right opportunity to land the canonical on main.

## Sequence executed (operator path-2 directive)

1. `gh pr close 1078 -R paiml/aprender` with rationale comment.
2. Created fresh aprender branch `contract/ccpa-poc-v1.24.0` from origin/main.
3. Copied companion's v1.23.0 contract YAML (`contracts/claude-code-parity-apr-v1.yaml`) into aprender's empty `contracts/` slot.
4. Applied 4 v1.24.0 amendments:
   - Status-prose at line 67 → M109 discharge integrated.
   - "What is NOT in this discharge" list item at line 808 → DISCHARGED with cross-refs.
   - Inline narrative at line 888 → "~60 GB" claim annotated as stale by 62 days.
   - New v1.23.0 → v1.24.0 status_history entry recording the discharge evidence.
5. `pv validate` clean (0 errors, 0 warnings).
6. Pushed + opened aprender PR #1613.

## Companion-side follow-up

This PR is companion-only (M132 row + M-counter bump). Once aprender#1613 merges:
- M133+ will refresh `contracts/pin.lock` with the squash commit hash + content sha256.
- Execute the M22 5-step ritual (4 cross-reference surface bumps + mirror byte-for-byte).
- Add an M-row recording the v1.23.0 → v1.24.0 sync.

## Verification

- bash scripts/check-doc-drift.sh → 0 drifts at tail M132
- bash scripts/test-doc-drift.sh → 14 / 14 drift classes still caught
- pv validate contracts/claude-code-parity-apr-v1.yaml → 0 errors

**No detector extension. No companion-side contract bump in this PR** (deferred to M133+).

Refs PMAT-037, #117, paiml/aprender#1078 (CLOSED), paiml/aprender#1613 (OPEN).

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…l once aprender#1613 merges (#119)

Refs PMAT-037, #118, paiml/aprender#1613.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…oses M128-M133 sequence (#120)

## Summary

Closes the M128-M133 sequence with the M22 5-step ritual on the companion side after aprender PR #1613 merged the v1.24.0 contract on aprender main.

## Aprender side (PR #1613, squash 9881c3f56, MERGED 2026-05-10T20:50:49Z)

Authored `contracts/claude-code-parity-apr-v1.yaml` v1.24.0 directly on aprender main as the FIRST canonical landing — replaces the closed PR #1078 (M0 mirror, "PR-pinned canonical" anomaly per companion-repo M130). v1.24.0 amendments to the v1.23.0 baseline:

1. Status-prose at line 67 → M109 cosine-vs-HF-FP16 discharge integrated.
2. "What is NOT in this discharge" list item at line 808 → DISCHARGED with cross-refs to aprender PR #1597 squash 3fb04ef86.
3. Inline narrative at line 888 → "~60 GB HF download" claim annotated as stale by 62 days.
4. New v1.23.0 → v1.24.0 status_history entry recording the discharge evidence.

## Companion side (this PR, M22 5-step ritual)

(a) `contracts/pin.lock` refreshed:
    - aprender_commit:    16f25af06 → 9881c3f56
    - aprender_branch:    feat/claude-code-parity-apr-poc-spec → main
    - aprender_pr:        1078 (OPEN) → 1613 (MERGED)
    - contract_sha256:    7818bd73... → ed5a90792b...
    - last_synced_utc:    2026-05-02T13:50:00Z → 2026-05-10T20:50:49Z
    - note prose updated with M134-context

(b) `contracts/claude-code-parity-apr-v1.yaml` mirrored byte-for-byte from aprender (sha256 verified).

(c) README.md badge `v1.23.0` → `v1.24.0` + status text "Contract at v1.24.0".

(d) CONTRIBUTING.md `Status as of v1.23.0` → `v1.24.0`.

(e) Top spec § Completeness summary headline `contract v1.23.0 ACTIVE_RUNTIME` → `v1.24.0 ACTIVE_RUNTIME` with M134-mirror cross-reference.

(f) `scripts/test-doc-drift.sh` corruption tests #4 (README) and #5 (CONTRIBUTING) updated to expect `v1.24.0` baseline.

## Why M134 is high-impact

M118-M133 was 16 PRs of kaizen-on-spec-prose. M134 is the FIRST contract version bump in this session — actual gate-bearing artifact change. The cumulative M128-M133 sequence walked the M22 5-step ritual phases:

- M128: surfaced the contract-prose drift.
- M130: surfaced the structural blocker (contract not on aprender main).
- M131: in-flight, attempted-merge of #1078.
- M132: path-2 pivot (close #1078, author fresh from main).
- M134: ritual closure — pin.lock + mirror + 4 cross-references.

Removes the "PR-pinned canonical" anomaly the spec carried since M0; future contract bumps follow standard M22 ritual without from-PR-branch indirection.

## Verification

- `pv validate contracts/claude-code-parity-apr-v1.yaml` → 0 errors, 0 warnings
- `bash scripts/check-doc-drift.sh` → 0 drifts at tail M134; v1.24.0 matches all 4 cross-references
- `bash scripts/test-doc-drift.sh` → 14 / 14 drift classes still caught (after meta-test #4+#5 baseline updates)
- `bash scripts/pin-check.sh` → sha256 matches between mirror + pin.lock
- 13/13 falsification gates remain green; 30/30 fixtures remain at aggregate parity 1.0000

**Contract bump v1.23.0 → v1.24.0**.

Refs PMAT-037, paiml/aprender#1613 (MERGED), #119.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>