Skip to content

CK-QG1: enforce agent-kernel maintainability ratchet - #392

Merged
douglasmonsky merged 32 commits into
mainfrom
chore/ck-qg1-maintainability-ratchet
Aug 8, 2026
Merged

CK-QG1: enforce agent-kernel maintainability ratchet#392
douglasmonsky merged 32 commits into
mainfrom
chore/ck-qg1-maintainability-ratchet

Conversation

@douglasmonsky

Copy link
Copy Markdown
Owner

Summary

  • add the repository-private normalized replacement-kernel maintainability baseline
  • enforce deterministic C/B/B findings against the exact baseline and origin/main without text exemptions
  • preserve the frozen spike check and wire focused ratchet coverage into the existing validation seam

Validation

  • focused checker, scope, schema, typing, and tests
  • just vc: 1,347 functional tests and 13 invariant tests passed
  • final sdist: 819,931 bytes (820,000-byte ceiling unchanged)
  • final allowance_read_p95_ms: 598.615998, invariants_only (non-gating noise)
  • staged GitNexus impact: LOW, no affected production process
  • exactly one independent final reviewer; all three in-scope findings fixed

Authority

CK-QG1 only, exact accepted CK-08R0 base 306cef3. No sibling lane, public surface, projection, join, or later-packet work.

@douglasmonsky

Copy link
Copy Markdown
Owner Author

CK-QG1 bounded blocker: hosted package-isolation CI correctly rejected the PR merge commit after origin/main advanced from the mandated CK-08R0 base 306cef3 to CK-08R2 merge 53ab22c (#391). CK-08R2 introduced two above-threshold normalized findings: query/page_executor.py:PageExecutionRequest (score 23, count 1) and query/page_executor.py:PageExecutionRequest.post_init (score 22, count 1). Both Python 3.10 and 3.14 jobs failed at the maintainability gate.

The CK-QG1 baseline remains exact to CK-08R0 (SHA-256 c490d954a5e9d09c61f884d51e3b9d3196af5615887f409c36f8469d1b2b6cf9). I did not broaden the baseline, add an exemption, weaken C/B/B thresholds, or refactor sibling production code because those would violate the lane locks. PR and retained worktree are preserved pending orchestrator disposition.

## Summary

- bound Candidate A model-call tail inserts by the runtime SQLite variable limit
- preserve canonical call identities while avoiding per-row JSON encoding in the timed tail
- add Python 3.10 portability coverage and endpoint identity assertions for the 2,000-call tail

## Root cause

The hosted `ordinary.2000_call_tail` path built one 36,000-variable SQLite INSERT. Python 3.10's SQLite binding limit rejected that statement with `sqlite3.OperationalError: too many SQL variables`, while the prior implementation did not inspect the runtime limit.

## Validation

- exact-base Python 3.10 baseline reproduces the `too many SQL variables` failure; corrected Python 3.10 and 3.14 focused suites pass
- 73-test Candidate A lifecycle/publication/performance/recovery profile passes on Python 3.10 and 3.14
- `just v` passes
- `just vc` passes, including distribution build and release verification
- all five frozen budgets and first-sample semantics remain unchanged

This PR is the CK-07R1A corrective prerequisite. It does not modify held PR #394 or shared roadmap authority.
CK-QG1A0 authority seam only; hosted CI passed.
Maintainer-approved package-budget supersession; all required hosted checks passed.
Integrates the reviewed CK-07R1A0 lifecycle-path authority on exact package-policy main. Preserves CK-07R1 BLOCKED status and the explicit one-run condition; no runtime or production qualification changes.
Authority transition accepted: CK-07R1 becomes Conditional Ready only after this merge and exact-main verification; PR #394 remains stale failed read-only.
Authority-only CK-07R1A0 source-digest freeze. Exact-main predecessor and retained candidate digests are frozen; witness remains read-only; maximum_new_end_to_end_runs=1 remains unspent and unavailable. Hosted Focused Evidence Console, Python 3.10, and Python 3.14 required jobs passed.
* docs: freeze lifecycle run invocation authority

* style: order lifecycle authority test imports
Squash merge after all required hosted CI jobs passed. Exact-main verification remains required before any worker revalidation or one-run qualification.
Squash merge after all required hosted CI checks passed.
* freeze CK-07R1 argv correction authority

* prove CK-07R1 exact argv without launch
* docs: converge roadmap orchestration

* docs: preserve run invocation authority binding
CK-QG1A exact-main reapplication. One-file authority-permitted complexity correction; all local and hosted validation passed.
CK-08R1A contract, schema, vectors, evidence schema, scope registration, and authority DAG transition. Local and hosted validation passed; no production answer implementation or evaluator included.
## What changed

Freeze the CK-08R3A successor decision at exact base `f3f376fc644a2e3d23c313dd6b7ca4b707c2998b`.

- Revoke `718ff7032d050b13cb7fac1f857d0c99879d0ef3b13c57c39b55514fc610a88b` as non-acceptable evidence.
- Permit one exact branch-pruned `UNION ALL` source identity plus exact evidence-order index and schema-contract identities.
- Preserve rate-card summary compatibility and valid-empty timeline/calls pages.
- Add machine-verifiable identity and negative-mutation authority tests.

## Why

Synthetic evidence reproduced the predecessor's forbidden inner temporary sorts and activity-cardinality growth, and the rejected successor regressed valid active `rate_card` paged scopes to unsupported errors. Source-only correction was insufficient under the strict no-temp-sort gate; the retained candidate's exact index plan removed the forbidden markers and held the decoded page bound at 8 rows for both 2,000 and 10,000 synthetic activities.

## Scope boundary

This PR contains only the authority JSON, CK-08R3A packet narrative, and authority tests. The candidate `service.py`, `analytical.sql`, and `storage/schema.py` remain uncommitted and preserved in the authority worktree; no implementation is accepted or merged here.

## Validation

- Focused authority tests: 13 passed.
- Clean exact-commit preflight: `just v` passed; `just vc` passed.
- GitNexus staged impact: low risk, zero affected execution processes.
- Staged secret scan: no leaks.
- Existing GitNexus index reports six pre-existing repository cycles; none are introduced by the staged docs/test set.
Squash merge of the narrowly scoped CK-08R3A schema/publication/accounting authority transition. Implementation remains permitted_not_accepted and Conditional Ready.
Squash merge of the final shared rank/provenance authority. CK-08R3A remains permitted_not_accepted; CK-07R1 remains blocked/no-launch.
Authority-only contract merge; CK-08R3A remains permitted_not_accepted and CK-07 remains blocked/no-launch.
Squash merge after focused authority review, exact cross-SQLite preflight, and green Console/Python 3.10/3.14 hosted CI. This authority remains permitted_not_accepted; it does not accept R3A or authorize CK-07/live/downstream operation.
* Bound evidence lifecycle queries by session

* docs(ck-08r3a): codify portable session merge contract

Squash merge after focused authority review, exact cross-SQLite preflight, and green Console/Python 3.10/3.14 hosted CI. This authority remains permitted_not_accepted; it does not accept R3A or authorize CK-07/live/downstream operation.

* docs(ck08r3a): freeze portable plan branch ownership proof (#423)

* test: prove portable evidence plan branch ownership
Merge the hosted-green CK-08R3 synthetic evidence-scale qualification.
## What changed

This authority-only PR binds the exact CK-QG1 maintainability baseline transition caused by the already-accepted writer provenance implementation on exact main `479cc58a887ab49e1bf6fae90ed87cd1cf389fd5`.

- predecessor baseline: `c490d954a5e9d09c61f884d51e3b9d3196af5615887f409c36f8469d1b2b6cf9`
- successor baseline: `fda777e28db7a0696f29b55c9d694f99d987413b206d8e323f217b4fa6a73ad5`
- exact transition: `publication/writer.py:PublicationWriter._validate_turn_provenance`, score `35`, count `1`
- accepted source: writer SHA `13da341fc2a3c50d8d7de7fd6a6fc2b0aca0dbc832a9b56597cd96ab67d17488`, introduced by accepted PR #417 commit `38537f6cee42ad4ba2fb6e45354e410053c7a7cd`

The machine-readable authority artifact includes byte-serializable predecessor/successor documents, exact metadata/tool/normalization identity, C/B/B thresholds, fail-closed new/worsened/improvement behavior, no text exemptions, privacy and spike invariants, and explicit negative mutations. It records current active package ceilings of 1,000,000/2,000,000 bytes while preserving CK-08R0’s historical 383,000/820,000 ratchet and the accepted package-budget supersession authority.

## Scope

Only authority JSON/schema, roadmap links and readiness wording, the repository scope helper, and focused authority/documentation/scope tests are included. No production source, maintainability checker, baseline file, candidate support bytes, or retained PR #392 witness is changed. CK-QG1 implementation acceptance is not granted.

## Validation

- held candidate’s actual `maintainability_failures` entry point: predecessor mismatch, exact successor match, byte mismatch, improvement without rebaseline, exact shrink, new finding, worsened finding, text exemption, and production-scope mutation matrix all passed as recorded
- `git diff --check`
- focused Ruff
- focused authority/documentation/scope tests: 35 passed
- full `tests/kernel`: 506 passed, 1 skipped
- `just vp`: passed
- `just v`: 1,406 passed, 1 skipped; performance invariants passed; Pyright and release safety passed
- `just vc`: package build and distribution release checks passed
- exactly one bounded independent reviewer; final correction review reported no material findings

## Handoff and acceptance boundary

After this PR is squash-merged and fresh exact-main identities are verified, coordinator may instruct the existing CK-QG1 worker to resume in a new latest-exact-main worktree and reuse PR #392. The held candidate remains read-only until then. No new authority task, implementation acceptance, CK-08RG/CK-09 dispatch, or live operation is authorized by this PR.
@douglasmonsky
douglasmonsky merged commit 68050b9 into main Aug 8, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant