Repository navigation
Conversation
Tracked infrastructure/*.py is 1359 (was 1356); project-scope/publishing collection literals regenerate with it (1554/1262). Rendered by collect_facts/render_counts_doc; the counts.py --write path stays blocked by the separately-owned stale coverage provenance, which this PR deliberately does not touch.
|
AGEINT 0.2 integration found a native release-blocking bibliography boundary at 5e6caba: a real BibTeX missing-style run exited 2, process_bibliography returned true, and compile_latex_manuscript replaced a valid published PDF with one lacking its bibliography. The isolated codex/ageint-renderer-0-2-20261107 branch fixes this in the SDK, adds genuine valid/multifile/failure/prior-PDF preservation controls, and includes the nested-image registry identity fix. Its preparatory commit is bfe49ab; push is being retried after a configuration-revision refusal. No after-fix acceptance is claimed yet. The existing candidate checkout and its running workflows are untouched. Please incorporate this consumer fix before the 5.1 Source freeze and renew the four-target policy census for the changed/new native families; do not reuse earlier census or acceptance as proof for these changes. Historical tags remain unchanged. |
|
AGEINT consumer correction update: PR #289 now contains corrective commit |
|
Consumer integration update: PR #289 now contains immutable Source |
|
AGEINT consumer qualification update: PR #289 is now at |
|
Consumer qualification remains on #289 at |
|
PR #289 now retains the genuine four-target authored policy and the qualified cold-import fix at |
Prepare the next coordinated SDK release before generating its final evidence. The existing Source-owned explicit minor transaction changes Root 5.0.2 → 5.1.0 and all 25 public exemplars' SDK requirements, compatibility bindings, local editable SDK lock records and manuscript platform bindings. Exemplar own versions and third-party locks are preserved.
The 77-file transaction was actually planned, checked and applied at the marker-bearing Source
538e5078f91011d3a2ad6e49a48c145828810f30, with plan SHA-256148607b9b5e69d0536df96b7b15fe177575da8b7c83cc3c197cdb61aa1a3306dand an independent original-byte journal. Eleven authored/generated release paths update current metadata/status, versioned notes and editable SVG/PNG with alt text. The notes date preparation status explicitly; the artwork describes exact-source acceptance as a requirement.This draft currently includes #279 as an ancestor. Merge #279 only after its genuine full producer and separate downloaded-carrier consumer pass at the same frozen SHA, then integrate that gated main here. The new Root census/authoring workflow and a genuine exhaustive reviewed policy refresh are also required before final Source qualification.
Validation: all 26 actual offline uv lock checks, all 26 pytest configurations/markers/selection options preserved, all third-party dependency records preserved, Root 5.1 plus 25 source-version bindings, owner status generation/freshness, full public Ruff lint/format on 5,320 files, and visual SVG/PNG review passed with Source unchanged. Local installed SDK remains authentic 4.4; genuine installed 5.1 proof belongs to hosted CI.
The unchanged config guard currently refuses exactly 15 tracked publication copies still binding 5.0.2. They must be genuinely refreshed in provider order with the original three publication guards. No generated-copy rewrite, coverage remeasurement/import, full release acceptance, tag or release is claimed by this metadata preparation. After real all 25 measurements at committed C, import the actual literals/provenance while HEAD remains C, commit D, and obtain unchanged-output all 25 rebind evidence before final exact-main acceptance.
Preserve v5.0.0, v5.0.1 and v5.0.2 unchanged; v5.0.2 receives no retroactive GitHub Release.