Checkpoint Agnir v1.0.2 stable publication

.agnir/evidence/2026-09-18-v1.0.2-stable-publication.md

@@ -0,0 +1,88 @@
+# Agnir v1.0.2 stable publication
+
+Date: 2026-09-18
+
+## Authorization
+
+The Principal explicitly authorized publication with the command: **“那就发布v1.0.2”**.
+
+The authorized release scope was limited to the already accepted ChatGPT Project locator-only packaging hardening. No Core/profile semantic expansion was authorized.
+
+## Published result
+
+Agnir `v1.0.2` is published as a stable non-prerelease release.
+
+- publication-arm / stable source revision: `b5626394ec40a5cb7a28c01892acde07cc0adc8e`;
+- tag: `v1.0.2` -> `b5626394ec40a5cb7a28c01892acde07cc0adc8e`;
+- GitHub Release id: `391529372`;
+- Release name: `Agnir v1.0.2`;
+- draft: `false`;
+- prerelease: `false`;
+- published at: `2026-09-18T14:14:18Z`;
+- publication workflow: `35354941029` — success;
+- repository/conformance job: `105631886209` — success;
+- stable publication job: `105631955191` — success;
+- GitHub `releases/latest`: `v1.0.2`.
+
+## Release path
+
+Accepted implementation and release preparation receipts:
+
+- locator-only implementation PR: `#58`;
+- implementation merge: `2c62d026c48405c3e299f0f57d6a674b3f6f9e1c`;
+- implementation post-merge conformance: `35353464865` — success;
+- Principal acceptance checkpoint: `4fde39128e5edf3fba3d7906a279918b1c38b7c2`;
+- acceptance conformance: `35353700740`, repository job `105627739027` — success;
+- release candidate branch: `release/v1.0.2`;
+- pre-checkpoint candidate: `907479d79921a8733052adb3384a58270a79bee1`, run `35354730577`, job `105631181979` — success;
+- checkpointed candidate: `5aa07a6df0aafba641c21db1b8b7deb72a3c2393`, run `35354791926`, job `105631387633` — success;
+- release candidate PR: `#60`;
+- PR synthetic-merge conformance: `35354845337`, repository job `105631565095` — success;
+- authoritative release-preparation merge: `72177afbbe4e36945366faaa9096b6d9bbb04d88`;
+- authoritative pre-publication run: `35354894720`, repository job `105631729092` — success;
+- publication job on the ordinary release-preparation merge: skipped, as required;
+- zero-tree-change publication arm: `b5626394ec40a5cb7a28c01892acde07cc0adc8e` with exact message `release: publish v1.0.2 stable`.
+
+## Published product change
+
+The stable ChatGPT Project handoff is:
+
+```text
+Canonical Project: <owner/repository> (<ref>)
+At the first substantive turn of every new conversation, open it, read root AGENTS.md, and follow it before doing Project work.
+```
+
+This is a locator into the Project-owned activation route, not a replacement for continuity semantics.
+
+The durable recovery path remains:
+
+`AGENTS.md -> AGNIR.md -> AGNIR.yaml -> selected durable continuity`
+
+The release therefore removes duplicated execution-surface procedure while preserving Agnir continuity.
+
+## Compatibility boundary
+
+Unchanged:
+
+- Agnir Core: `1.0`;
+- profile: `repository-filesystem/1.0`;
+- Project identity semantics;
+- Continuity Lineage semantics;
+- checkpoint/reconciliation semantics;
+- historical Core/profile `0.1` and `0.2` compatibility/migration surfaces.
+
+This is a PATCH-level distribution/onboarding release.
+
+## Immutable history checks
+
+Publication workflow and direct host readback verified:
+
+- previous stable `v1.0.1` remains exactly `f56d25b22997c259c660651e7357334b063093e1`;
+- `v1.0.0` remains exactly `6d16dcfd17b8e9f22fd25804e22b9f8a516d06c3`;
+- accepted `v1.0.0-rc.1` remains exactly `092945289f1a0a9803e4fe0583104aa380ceaadc`.
+
+Published tags remain immutable by Project policy.
+
+## Post-publication reconciliation
+
+Post-publication continuity and public documentation may advance authoritative `main` beyond the immutable `v1.0.2` tag. Such commits record publication truth; they do not change the source that was published.

.agnir/next-actions.md

@@ -1,17 +1,16 @@
 # Agnir Next Actions
 
-Agnir `v1.0.1` remains the published latest stable release while repository source `1.0.2` is staged as an explicitly authorized PATCH publication candidate. Core/profile remain `1.0` / `repository-filesystem/1.0`.
-
-1. **Complete and publish the v1.0.2 candidate.** Require green candidate conformance, merge/reconcile onto authoritative `main`, require green post-merge conformance, then create an exact empty publication-arm commit `release: publish v1.0.2 stable`. Accept publication only after tag/Release/latest readback and immutable earlier-tag checks pass.
-2. **After successful publication, reconcile stable metadata.** Update `AGNIR.yaml`, RELEASE/versioning/README surfaces, State/Next Actions, and publication Evidence so `v1.0.2` becomes the recorded latest stable while the immutable release tag continues to point to the exact publication-arm revision.
-3. **Observe the accepted locator-only handoff in the next genuine fresh ChatGPT Project initialization.** Treat a future verbose handoff as a packaging regression; do not solve it by duplicating Agnir operational semantics back into Project Instructions.
-4. **Optionally repair the v1.0.1 GitHub Release-body wording.** One historical cosmetic sentence omitted the literal `AGNIR.md`; any repair must update host metadata only and must not move/recreate `v1.0.1`.
-5. **Complete human visual review of the refined Install-section two-session preview.** PR `#55` is published. Confirm the live install area now reads unmistakably as two different Agent sessions: Session A above, Fresh Session B below, with the “open a fresh session” divider, consistent four-point Agent icon, clean desktop/mobile balance, and usable dark/light plus English / Simplified Chinese / Japanese / Korean presentation. Also confirm the hero comparison caption now reads **“两个新会话都只收到一句：‘继续。’ 但大有不同。”** in Simplified Chinese. This is public-surface polish, not a Core or adoption gate.
-6. **Recruit the first external design users and collect material adoption evidence.** The synchronized split-screen fresh-session demo v3 has passed Principal human visual review and is the primary first-contact proof surface. Prioritize genuine external cold-start resumes, second-session value, cross-Executor cases, new execution surfaces, repeat use, and independently built integrations.
-7. **Keep brand/public-surface truth locked.** README, website, adoption/demo and social materials may consume approved brand assets/deterministic derivatives but must not reinterpret approved identity or Core semantics.
-8. **Keep merged-head cleanup enabled.** `main` remains the sole intended long-lived authoritative branch; completed staging branches should remain retired after their material result and evidence are durably represented.
-9. **Shift active product execution back to Svif where appropriate.** Svif owns its own canonical continuity and ChatGPT/Plugins publication path; do not smuggle Svif changes into Agnir maintenance.
-10. **Keep FishUp production publication separate.** No FishUp main advancement without separate authorization.
+Agnir `v1.0.2` is published and verified as the latest stable repository/distribution release. Core/profile remain `1.0` / `repository-filesystem/1.0`.
+
+1. **Operate the 1.0 line in stable-maintenance mode.** Preserve Core/profile 1.0 semantics and historical 0.1/0.2 compatibility/migration surfaces. Future patch releases must not silently expand or redefine the stable contract.
+2. **Observe the accepted locator-only handoff in the next genuine fresh ChatGPT Project initialization.** Treat a future verbose handoff as a packaging regression; do not solve it by duplicating Agnir operational semantics back into Project Instructions.
+3. **Optionally repair the historical v1.0.1 GitHub Release-body wording.** One cosmetic sentence omitted the literal `AGNIR.md`; any repair must update host metadata only and must not move/recreate `v1.0.1`.
+4. **Complete human visual review of the refined Install-section two-session preview.** PR `#55` is published. Confirm the live install area now reads unmistakably as two different Agent sessions: Session A above, Fresh Session B below, with the “open a fresh session” divider, consistent four-point Agent icon, clean desktop/mobile balance, and usable dark/light plus English / Simplified Chinese / Japanese / Korean presentation. Also confirm the hero comparison caption now reads **“两个新会话都只收到一句：‘继续。’ 但大有不同。”** in Simplified Chinese. This is public-surface polish, not a Core or adoption gate.
+5. **Recruit the first external design users and collect material adoption evidence.** The synchronized split-screen fresh-session demo v3 has passed Principal human visual review and is the primary first-contact proof surface. Prioritize genuine external cold-start resumes, second-session value, cross-Executor cases, new execution surfaces, repeat use, and independently built integrations.
+6. **Keep brand/public-surface truth locked.** README, website, adoption/demo and social materials may consume approved brand assets/deterministic derivatives but must not reinterpret approved identity or Core semantics.
+7. **Keep merged-head cleanup enabled.** `main` remains the sole intended long-lived authoritative branch; completed staging/checkpoint branches should remain retired after their material result and evidence are durably represented.
+8. **Shift active product execution back to Svif where appropriate.** Svif owns its own canonical continuity and ChatGPT/Plugins publication path; do not smuggle Svif changes into Agnir maintenance.
+9. **Keep FishUp production publication separate.** No FishUp main advancement without separate authorization.
 
 ## Install preview split-session refinement receipts
 
@@ -98,6 +97,24 @@ Agnir `v1.0.1` remains the published latest stable release while repository sour
 - artifact digest: `sha256:15bd2907feec1ab772f7484fe040f42fb0b717db0e6c91c45240f013050b1fab`;
 - initial publication evidence: `.agnir/evidence/2026-09-14-canonical-fresh-session-demo.md`.
 
+## v1.0.2 stable publication receipts
+
+- locator simplification implementation PR: `#58`, merge `2c62d026c48405c3e299f0f57d6a674b3f6f9e1c`;
+- Principal acceptance checkpoint: `4fde39128e5edf3fba3d7906a279918b1c38b7c2`;
+- release candidate PR: `#60`, authoritative merge `72177afbbe4e36945366faaa9096b6d9bbb04d88`;
+- authoritative pre-publication conformance: run `35354894720`, repository job `105631729092` — success;
+- publication arm / stable source: `b5626394ec40a5cb7a28c01892acde07cc0adc8e`;
+- publication workflow: `35354941029` — success;
+- publication repository job: `105631886209` — success;
+- stable publication job: `105631955191` — success;
+- stable tag: `v1.0.2` -> `b5626394ec40a5cb7a28c01892acde07cc0adc8e`;
+- GitHub Release id: `391529372`;
+- published at: `2026-09-18T14:14:18Z`;
+- latest stable readback: `v1.0.2`;
+- previous `v1.0.1`: unchanged at `f56d25b22997c259c660651e7357334b063093e1`;
+- `v1.0.0`: unchanged at `6d16dcfd17b8e9f22fd25804e22b9f8a516d06c3`;
+- accepted RC `v1.0.0-rc.1`: unchanged at `092945289f1a0a9803e4fe0583104aa380ceaadc`;
+- publication evidence: `.agnir/evidence/2026-09-18-v1.0.2-stable-publication.md`.
 ## v1.0.1 stable publication receipts
 
 - implementation PR: `#50` — merged;

.agnir/state.md

@@ -2,9 +2,42 @@
 
 Durable continuity belongs to the Project.
 
-## Stable v1.0.1 publication
+## Stable v1.0.2 publication
 
-Agnir `v1.0.1` is now **published, verified, and the latest stable repository/distribution release**.
+Agnir `v1.0.2` is **published, verified, and the latest stable repository/distribution release**.
+
+Accepted stable publication receipts:
+
+- publication authorization: Principal command `发布v1.0.2` / `那就发布v1.0.2`;
+- publication-arm / immutable stable tag revision: `b5626394ec40a5cb7a28c01892acde07cc0adc8e`;
+- immutable stable tag: `v1.0.2` -> `b5626394ec40a5cb7a28c01892acde07cc0adc8e`;
+- GitHub Release id: `391529372`;
+- Release state: non-draft, non-prerelease;
+- published at: `2026-09-18T14:14:18Z`;
+- publication workflow: `35354941029` — success;
+- repository/conformance job: `105631886209` — success;
+- stable publication job: `105631955191` — success;
+- GitHub `releases/latest`: `v1.0.2`;
+- previous stable `v1.0.1` remains exactly `f56d25b22997c259c660651e7357334b063093e1`;
+- `v1.0.0` remains exactly `6d16dcfd17b8e9f22fd25804e22b9f8a516d06c3`;
+- accepted `v1.0.0-rc.1` remains exactly `092945289f1a0a9803e4fe0583104aa380ceaadc`.
+
+Repository/distribution `1.0.2` is a PATCH-level execution-surface onboarding/packaging hardening over `1.0.1`. It publishes the Principal-accepted locator-only ChatGPT Project handoff while leaving Core `1.0`, `repository-filesystem/1.0`, Project identity, Continuity Lineage, checkpoint semantics, and historical compatibility lines unchanged.
+
+The accepted persistent ChatGPT Project handoff is:
+
+```text
+Canonical Project: <owner/repository> (<ref>)
+At the first substantive turn of every new conversation, open it, read root AGENTS.md, and follow it before doing Project work.
+```
+
+Continuity remains Project-owned behind `AGENTS.md -> AGNIR.md -> AGNIR.yaml -> selected durable continuity`; the surface instruction is only the durable locator into that route.
+
+`VERSION`, `AGNIR.yaml extensions.agnir/release.repository_version`, and `agnir/operations.release` reconcile to repository/distribution `1.0.2`; `agnir/operations.applied_revision` records the immutable stable source revision `b5626394ec40a5cb7a28c01892acde07cc0adc8e`.
+
+## Previous stable v1.0.1 publication
+
+Agnir `v1.0.1` remains an **immutable previous stable release**. Its publication receipts remain historical evidence for the 1.0 line.
 
 Accepted stable publication receipts:
 
@@ -42,20 +75,17 @@ The GitHub Release body has one cosmetic omission: the intended literal `` `AGNI
 
 This is a repository-host presentation defect, not a package-integrity or protocol defect. It must not be repaired by moving/recreating the published tag. A future authorized metadata repair may update only the Release body while preserving release identity.
 
-## v1.0.2 publication candidate
+## v1.0.2 publication acceptance
 
-On 2026-09-18, the Principal explicitly authorized **publish `v1.0.2`** after accepting the locator-only ChatGPT Project bootstrap contract.
+The authorized PATCH release cycle is closed.
 
-The release scope is intentionally PATCH-only:
+Release preparation PR `#60` merged to authoritative `main` at `72177afbbe4e36945366faaa9096b6d9bbb04d88`. Post-merge conformance run `35354894720`, repository job `105631729092`, succeeded while the v1.0.2 publication job was correctly skipped.
 
-- publish the already accepted two-line ChatGPT Project locator handoff;
-- keep Project continuity behind `AGENTS.md -> AGNIR.md -> AGNIR.yaml -> selected durable continuity`;
-- add exact `v1.0.2` release packaging, conformance, and an authoritative-main publication gate;
-- preserve Core `1.0`, `repository-filesystem/1.0`, Project identity, Continuity Lineage, checkpoint semantics, and historical `0.1`/`0.2` compatibility.
+The separate zero-tree-change publication arm `b5626394ec40a5cb7a28c01892acde07cc0adc8e` used the exact commit message `release: publish v1.0.2 stable`. Workflow `35354941029` re-ran exact-source repository/full conformance, then publication job `105631955191` created and verified tag/Release/latest state.
 
-Candidate staging branch: `release/v1.0.2`. Repository source version is `1.0.2`; **latest stable remains `v1.0.1` until publication actually succeeds**. Publication is allowed only through an exact `main` commit message `release: publish v1.0.2 stable`, after candidate and authoritative-main conformance are green.
+Host readback confirms `refs/tags/v1.0.2` and Release `391529372` both target the exact arm revision, the Release is non-draft/non-prerelease, and `releases/latest == v1.0.2`. Immutable `v1.0.1`, `v1.0.0`, and `v1.0.0-rc.1` receipts remain unchanged.
 
-Accepted implementation inputs are PR `#58` / merge `2c62d026c48405c3e299f0f57d6a674b3f6f9e1c` and acceptance checkpoint `4fde39128e5edf3fba3d7906a279918b1c38b7c2`, with authoritative conformance run `35353700740` success.
+The release branch has been retired after merge. Post-publication metadata/document reconciliation may advance authoritative `main`, but it does not change the immutable source published as `v1.0.2`.
 
 ## Public product state
 

AGNIR.yaml

@@ -30,7 +30,7 @@ extensions:
       kind: "vcs-ref"
       selector: "refs/heads/main"
   agnir/release:
-    phase: "stable-v1.0.2-implemented-publication-pending"
+    phase: "stable-v1.0.2-published"
     repository_version: "1.0.2"
     core_contract: "spec/AGNIR_CORE_1_0.md"
     profile_contract: "profiles/REPOSITORY_FILESYSTEM_1_0.md"
@@ -42,28 +42,28 @@ extensions:
     implementation_verification_run: 34255207555
     implementation_verification_job: 102159143123
     staging_ref_retired: true
-    publication_arm_revision: "f56d25b22997c259c660651e7357334b063093e1"
-    stable_tag: "v1.0.1"
-    stable_revision: "f56d25b22997c259c660651e7357334b063093e1"
-    stable_release_id: 385176185
-    stable_published_at: "2026-09-09T02:02:14Z"
-    publication_run: 34301559338
-    publication_repository_job: 102309347343
-    publication_job: 102309386242
-    previous_stable_tag: "v1.0.0"
-    previous_stable_revision: "6d16dcfd17b8e9f22fd25804e22b9f8a516d06c3"
-    previous_stable_release_id: 383612171
-    previous_stable_published_at: "2026-09-06T14:23:58Z"
-    previous_publication_run: 34039014354
-    previous_publication_repository_job: 101502237380
-    previous_publication_job: 101502271312
+    publication_arm_revision: "b5626394ec40a5cb7a28c01892acde07cc0adc8e"
+    stable_tag: "v1.0.2"
+    stable_revision: "b5626394ec40a5cb7a28c01892acde07cc0adc8e"
+    stable_release_id: 391529372
+    stable_published_at: "2026-09-18T14:14:18Z"
+    publication_run: 35354941029
+    publication_repository_job: 105631886209
+    publication_job: 105631955191
+    previous_stable_tag: "v1.0.1"
+    previous_stable_revision: "f56d25b22997c259c660651e7357334b063093e1"
+    previous_stable_release_id: 385176185
+    previous_stable_published_at: "2026-09-09T02:02:14Z"
+    previous_publication_run: 34301559338
+    previous_publication_repository_job: 102309347343
+    previous_publication_job: 102309386242
     accepted_rc_tag: "v1.0.0-rc.1"
     accepted_rc_revision: "092945289f1a0a9803e4fe0583104aa380ceaadc"
     accepted_rc_release_id: 383536840
     accepted_rc_publication_run: 34026167762
     accepted_rc_fresh_attempt: 2
     accepted_rc_acceptance_checkpoint: "afc07d062b957e8dbfe3f859834c787e64aa52be"
-    previous_latest_stable: "v1.0.0"
+    previous_latest_stable: "v1.0.2"
     latest_stable: "v1.0.1"
     candidate_scope: "chatgpt-project-locator-only"
     candidate_implementation_pr: 58
@@ -72,10 +72,10 @@ extensions:
     candidate_acceptance_checkpoint: "4fde39128e5edf3fba3d7906a279918b1c38b7c2"
     candidate_acceptance_verification_run: 35353700740
     candidate_acceptance_verification_job: 105627739027
-    publication_status: "v1.0.1-published-v1.0.2-candidate"
+    publication_status: "published-verified"
     target_ref: "refs/heads/main"
   agnir/operations:
     distribution: "agnir-agent-skill"
-    release: "1.0.1"
+    release: "1.0.2"
     source: "iorLab/agnir"
-    applied_revision: "f56d25b22997c259c660651e7357334b063093e1"
+    applied_revision: "b5626394ec40a5cb7a28c01892acde07cc0adc8e"