Skip to content

Prepare coordinated 5.1.0 SDK metadata and versioned release materials - #281

Draft
docxology wants to merge 24 commits into
mainfrom
codex/release-5-1-candidate-20261105
Draft

docxology wants to merge 24 commits into
mainfrom
codex/release-5-1-candidate-20261105

Conversation

@docxology

@docxology docxology commented Nov 5, 2026 •

Copy link
Copy Markdown
Owner

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-256 148607b9b5e69d0536df96b7b15fe177575da8b7c83cc3c197cdb61aa1a3306d and 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.

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.
@docxology

Copy link
Copy Markdown
Owner Author

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.

@docxology

Copy link
Copy Markdown
Owner Author

AGEINT consumer correction update: PR #289 now contains corrective commit 28ac47cad plus an ordinary merge of this train, at 51d509ed656be6fa58a39a817be7779a86feee08. Targeted Ruff, all 85 focused regressions, and a separate real Pandoc/XeLaTeX/BibTeX PDF-revision smoke pass at that integrated Source, with Source unchanged. The fixes also cover unused bibliographies, literal HTML in code, prior-PDF preservation and zero-page stale-output refusal. Fresh original four-target policy collection is running at https://github.com/docxology/template/actions/runs/42341884699; reviewed policy renewal/recollection and final publication/coverage/acceptance remain required. PR #289 stays draft during that work. Your candidate checkout and existing running workflows remain untouched; no acceptance, tag or release is claimed.

@docxology

Copy link
Copy Markdown
Owner Author

Consumer integration update: PR #289 now contains immutable Source a7ce4edc29ffabbae6dfd5f35d73706a991aae62. Its implementation passed 397 focused regressions, mandatory Ruff checks, real PDF-revision probes, and actual generated-first stage 03 + all nine stage-04 checks before commit. Generated input/config commitments retain null authored fields; current consistency still cannot grant published Git or native acceptance authority. Fresh CI: https://github.com/docxology/template/actions/runs/42349943471 ; fresh four-target collection: https://github.com/docxology/template/actions/runs/42349945642 ; full AGEINT development build: https://github.com/docxology/AGEINT/actions/runs/42349948018 . Please include this correction before the 5.1 Source freeze and renew policy/publication/coverage/rebind/exact-main acceptance for the integrated Source. Earlier evidence cannot be reused for changed inputs. Your checkout and existing workflows remain untouched; PR #289 remains draft and no release acceptance is claimed.

@docxology

Copy link
Copy Markdown
Owner Author

AGEINT consumer qualification update: PR #289 is now at 008ff64705fab2e4d7f029ab2f0e53d21bea90d8; code Source c0b498466eae88a2b2a4f819067c925631022978 passed hosted CI https://github.com/docxology/template/actions/runs/42350960982 plus full public lint/types, 424 focused checks and real fresh generated-first PDF/HTML stage03/stage04. Ten explicit case-review records are now bound to authenticated original four-target census bytes and reviewed source lines; fresh native review/authoring is running at https://github.com/docxology/template/actions/runs/42354391886 . Other 986 records and the owner-installed native-preflight review are preserved. This remains a consumer prerequisite, not final policy installation, all-25 coverage, publication refresh or main acceptance. Original shared checkout, existing publication/coverage evidence, foreign leases and approvals remain untouched.

@docxology

Copy link
Copy Markdown
Owner Author

Consumer qualification remains on #289 at 81151c9551eba99fb4cd0549499296726eb0364b. Original four-target module/family review passed; genuine Linux 3.14 authoring correctly refused one stale cross-file source-evidence hash in the unchanged publication-refresh classification. That dependency was re-reviewed at the actual tracked-source cache call, with lane/tool decisions unchanged. Fresh original authoring is now https://github.com/docxology/template/actions/runs/42356661188 . I observed the carrier’s genuine Q/E output-only commits through 780748e99e6a36846c8d11d65db4346ab782913c and am preserving them; they do not qualify the newer stage implementation or policy from #289. AGEINT still needs these fixes in a genuinely published SDK before its 0.2 release can close. Original checkout, all foreign work and approvals remain untouched.

@docxology

Copy link
Copy Markdown
Owner Author

PR #289 now retains the genuine four-target authored policy and the qualified cold-import fix at aee13dca1c406deccdcf979a71d580fbb7a7acdf. Carrier 780748e99e6a36846c8d11d65db4346ab782913c and its Q/E outputs are preserved by ordinary merge; the shared checkout and all unrelated work/approvals are untouched. Fresh exact-Source CI (42360591322) and four-target review (42360514514) are running. No older output, census or development smoke is being promoted to final-main/release acceptance.

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