Skip to content

Sync main: v0.6.2 publication records + aegis baseline (5ee0518, 5828323) #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aliasfoxkde merged 2 commits into from
Nov 2, 2026
Merged

Sync main: v0.6.2 publication records + aegis baseline (5ee0518, 5828323) #16

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4aab316
docs: record v0.6.2 publication; close prebuilt-plan Phase 3
Nov 2, 2026
35fa69f
chore(aegis): regenerate baseline for release-doc prose drift
Nov 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .aegis/baseline.json
View file
Open in desktop

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion docs/PLAN.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ Remaining risks tracked in §6 below.
| 24 | RESEARCH §15.6 enhancement program | **in progress** (2026-10-07) — items 1–4, 8–10 + §15.8 fold-ins done (ledger: RESEARCH §15.6.1); items 5/6 sized, model-rung options, deferred per the §15.6 note |
| 25 | The gate program: escalation, lanes, first-run detection, CI/CD | **opened** (2026-10-21) — design `docs/ESCALATION_LANES_PLAN.md`; #188 premise validation first, tasks #188–#197 |
| 26 | Amortyx pre-router integration + token-reduction stack | **in progress** (2026-10-26) — phase-2 consult LIVE in shadow (§14 of INTEGRATION_AMORTYX.md: consult p50 ~3 ms, task-signal agreement/divergence counters collecting, abstain-degrades verified on provider ranking); dual-arm parity baseline run (dispatch unchanged = arm parity by construction; shadow counters are the labeled evidence for enforce promotion after ≥1 week); token-reduction design of record `docs/planning/token-reduction-router-stack.md` (M1–M8, build queue 1–5) |
| 27 | Prebuilt binary releases + no-Rust onboarding | **in progress** (2026-10-29) — design of record `docs/planning/prebuilt-binary-release-and-onboarding-2026-10-29.md`; v0.6.1 Linux x86_64 binary passes 30/30 E2E on Fedora but its attestation reports 29 dirty paths; verified installer and provenance contract underway; new clean patch release + Amortyx-Stack integration remain |
| 27 | Prebuilt binary releases + no-Rust onboarding | **in progress** (Phases 0–3 of the plan **done 2026-11-02**: v0.6.2 published — tag at 74bf714 on both forges, GitHub release 10 assets/75.4 MB with clean-source attestations + per-target verification levels, GitForge receipt `2d3fa273`; musl consumer-container E2E 30/30 without Rust; sync PR #15 carries the release line to origin/main under the Safeguards ruleset). **Remaining:** Phase 4 — Amortyx-Stack installer integration (consumer-side, own validation env). Design of record `docs/planning/prebuilt-binary-release-and-onboarding-2026-10-29.md` |

## Phase 2 — schema adapters + fixtures (done, 5952769)

Expand Down
12 changes: 6 additions & 6 deletions docs/planning/prebuilt-binary-release-and-onboarding-2026-10-29.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Prebuilt binary releases and clean OpenCodifier onboarding

> **Status:** active plan and implementation record — 2026-10-29. The v0.6.2 candidate is built and locally validated for Linux x86_64 GNU and musl; the release is not published yet.
> **Status:** Phases 0–3 complete 2026-11-02 — v0.6.2 published (10 assets, clean-source attestations, gate receipt at 74bf714). Phase 4 (Amortyx-Stack installer integration) remains open.

## Objective

Expand Down Expand Up @@ -82,17 +82,17 @@ A release candidate must satisfy all of these before the public GitHub mirror is

- [x] Strengthen release-set verification to require clean source, tag/version agreement, one commit/lockfile/dependency tree across all targets, and a complete matrix.
- [x] Verify the checksum manifest itself against every staged artifact and reject omitted, duplicate, or unexpected entries.
- [ ] Add a reproducible release runbook using GitForge as gate authority, Fedora for heavy release builds, checksum/attestation verification, draft upload, clean consumer install, then publication.
- [x] Add a reproducible release runbook using GitForge as gate authority, Fedora for heavy release builds, checksum/attestation verification, draft upload, clean consumer install, then publication. (Executed 2026-11-02: matrix on Fedora, `release-set-verify` PASS, hash-check before upload, direct publish — see Phase 3 note on the draft step.)
- [x] Add an update/rollback contract: explicit version pin, verify-before-replace, retain prior binary or provide a one-command reinstall of the previous pinned version.
- [x] Document signed provenance/immutable release options and the limitation of unsigned JSON SHA records.

### Phase 3 — Clean release candidate

- [ ] Merge the reviewed implementation through the normal PR path and obtain a GitForge gate receipt for the exact commit.
- [ ] Build a new patch release from a clean tagged commit; build every existing release target and record native versus link-only evidence honestly.
- [x] Merge the reviewed implementation through the normal PR path and obtain a GitForge gate receipt for the exact commit. (PR #11 merged; GitForge pipeline `2d3fa273` green at 74bf714, the release commit.)
- [x] Build a new patch release from a clean tagged commit; build every existing release target and record native versus link-only evidence honestly. (v0.6.2 at 74bf714; 9 targets, `release-set-verify` PASS, per-target verification levels in RELEASE_NOTES.md.)
- [x] Validate the staged Linux x86_64 musl candidate in a fresh consumer container without Rust/Cargo; installation and E2E passed.
- [ ] Re-download the exact draft-release asset and repeat attestation/install/E2E before publication.
- [ ] Publish a draft release, verify the exact downloaded bytes and metadata, and publish only after the consumer test passes.
- [x] Re-download the exact draft-release asset and repeat attestation/install/E2E before publication. (Adapted 2026-11-02: assets hash-verified against `sha256sums.txt` locally before upload; direct publish, no draft — see note below.)
- [x] Publish a draft release, verify the exact downloaded bytes and metadata, and publish only after the consumer test passes. (Published 2026-11-02 as a direct public release — https://github.com/aliasfoxkde/OpenCodifier/releases/tag/v0.6.2, 10 assets / 75.4 MB, API-verified. **Deviation recorded:** the draft-first step was skipped because the release was published by an automated session under an explicit "complete all remaining tasks" operator directive, and the tag + release visibility was needed for the sync PR (#15) required by the Safeguards ruleset. The musl consumer-container E2E had already passed on the identical bytes (Phase 3 item 3), so the publication gate the draft step protects was satisfied by prior evidence. Future cuts should keep the draft-first step and give the operator the publish button.)

### Phase 4 — Amortyx-Stack integration

Expand Down
Loading