@t275005746/gse 0.1.1 → 0.2.0

package/.gse/releases/public-github-release-v0.1.2.md

@@ -0,0 +1,49 @@
+# Public Channel Publication Record
+
+Publication status: accepted
+
+Channel type: github-release
+
+Channel name: GitHub Release
+
+Channel URL: https://github.com/275005746/gse/releases/tag/v0.1.2
+
+Package or listing version: v0.1.2
+
+Artifact digest: not-applicable
+
+Review or approval status: published
+
+Evidence owner: 275005746
+
+Evidence date: 2026-07-10
+
+Evidence URL or run id: https://github.com/275005746/gse/releases/tag/v0.1.2
+
+## Verification
+
+Verification command: gh release view v0.1.2 --repo 275005746/gse --json tagName,url,isDraft,isPrerelease
+
+Verification result: passed
+
+## Acceptance
+
+Evidence status: accepted
+
+Accepted by: 275005746
+
+Accepted at: 2026-07-10
+
+## Boundaries
+
+- Does this prove public registry publication? false
+- Does this prove marketplace approval? unknown
+- Does this prove installability from the channel? true
+
+## Residual Risk
+
+- GitHub Release proves source release visibility; npm remains the package registry install channel.
+
+## Next Action
+
+- Keep GitHub Release v0.1.2 aligned with npm @t275005746/gse@0.1.2.

package/.gse/releases/public-registry-publication-npm.md

@@ -1,49 +1,49 @@
-# Public Channel Publication Record
-
-Publication status: accepted
-
-Channel type: package-registry
-
-Channel name: npm
-
-Channel URL: https://www.npmjs.com/package/@t275005746/gse
-
-Package or listing version: 0.1.0
-
-Artifact digest: sha512-DcnRp6yZv/LjON/uowlze5yuV2JIAWfOD9GGQhVpIGX5IgmA7r9j2FkIDFT3n4abSZ5q/3SH7rh56gICFrml3Q==
-
-Review or approval status: published
-
-Evidence owner: t275005746
-
-Evidence date: 2026-07-08
-
-Evidence URL or run id: https://www.npmjs.com/package/@t275005746/gse
-
-## Verification
-
-Verification command: node scripts/validate-gse.mjs --root . --json
-
-Verification result: passed
-
-## Acceptance
-
-Evidence status: accepted
-
-Accepted by: 275005746
-
-Accepted at: 2026-07-08
-
-## Boundaries
-
-- Does this prove public registry publication? true
-- Does this prove marketplace approval? unknown
-- Does this prove installability from the channel? true
-
-## Residual Risk
-
-- Public channel publication is not accepted until real external evidence is attached.
-
-## Next Action
-
-- Attach public channel publication evidence and re-run final readiness.
+# Public Channel Publication Record
+
+Publication status: accepted
+
+Channel type: package-registry
+
+Channel name: npm
+
+Channel URL: https://www.npmjs.com/package/@t275005746/gse
+
+Package or listing version: 0.1.2
+
+Artifact digest: sha512-QiMQGnpM515sR4/dEz4q8+Lau0m026Pxo83lBshH2aVoWw+ooR8W8Vz2nM4bSWqEC1rbkP95WAYS9GA5g4yYUA==
+
+Review or approval status: published
+
+Evidence owner: 275005746
+
+Evidence date: 2026-07-10
+
+Evidence URL or run id: https://www.npmjs.com/package/@t275005746/gse/v/0.1.2
+
+## Verification
+
+Verification command: cmd /c npm view @t275005746/gse@0.1.2 name version dist.integrity dist-tags --json
+
+Verification result: passed
+
+## Acceptance
+
+Evidence status: accepted
+
+Accepted by: 275005746
+
+Accepted at: 2026-07-10
+
+## Boundaries
+
+- Does this prove public registry publication? true
+- Does this prove marketplace approval? unknown
+- Does this prove installability from the channel? true
+
+## Residual Risk
+
+- Native host slash-command support remains a separate host invocation claim.
+
+## Next Action
+
+- Use npm @t275005746/gse@0.1.2 as the public install baseline for post-release sanity and downstream project adoption.

package/.gse/state.json

@@ -1,26 +1,148 @@
-{
-  "schemaVersion": 1,
-  "projectName": "gse",
-  "mode": "enterprise",
-  "canonicalPlan": ".gse/gse-design-master-plan.md",
-  "phase": "release",
-  "currentSlice": {
-    "id": "GSE-108-public-registry-publication",
-    "outcome": "Complete the real public registry publication gate for @t275005746/gse, then record accepted publication evidence.",
-    "status": "verified",
-    "nextAction": "Collect real native slash-command host evidence for /gse continue, record it as accepted host invocation evidence, then re-run the public acceptance doctor."
-  },
-  "toolStatuses": {
-    "browser": "unknown",
-    "lsp": "unknown",
-    "mcp": "unknown",
-    "subagents": "unknown",
-    "ci": "verified-public"
-  },
-  "lastEvidence": ".gse/evidence/2026-07-07.md",
-  "residualRisks": [
-    "Native slash-command support remains external-required until a real host runtime proves native /gse invocation with accepted evidence.",
-    "Do not treat portable text-command routing, generated command pointers, package dry-runs, local tarball installs, or release bundles as public registry publication or native slash-command evidence.",
-    "Use /gse doctor and audit-public-acceptance-readiness.mjs as the current source of truth for pending final-form gates."
-  ]
-}
+{
+  "schemaVersion": 1,
+  "projectName": "gse",
+  "mode": "enterprise",
+  "canonicalPlan": ".gse/gse-design-master-plan.md",
+  "phase": "final-form",
+  "currentSummary": {
+    "status": "support-slice-boundary-verified",
+    "localEngineeringReadiness": 100,
+    "fullFinalFormReadiness": 100,
+    "publicAccepted": "verified",
+    "pendingExternalGate": null,
+    "currentPlan": "GSE-155 is verified in source: /gse continue now surfaces currentSlice.supportSliceBoundary for deliberate product maintenance and suppresses only soft CP23 when its narrow boundary is declared. Keep /gse doctor and audit-public-acceptance-readiness.mjs as final-form source of truth."
+  },
+  "currentSlice": {
+    "id": "GSE-155-support-slice-boundary",
+    "outcome": "GSE /gse continue now lets product projects explicitly bound a deliberate support slice so CP23 distinguishes bounded maintenance from unbounded repeated support work.",
+    "status": "verified",
+    "nextAction": "Use supportSliceBoundary only for deliberate bounded product maintenance; otherwise select a user-visible product delta and preserve native slash-command evidence as a host-specific external gate."
+  },
+  "toolStatuses": {
+    "browser": "unknown",
+    "lsp": "unknown",
+    "mcp": "unknown",
+    "subagents": "unknown",
+    "ci": "documented"
+  },
+  "lastEvidence": ".gse/evidence/2026-07-11.md",
+  "blockedGates": [],
+  "nextChecks": [
+    "node scripts/run-gse-command.mjs --root . --target . --command \"/gse doctor\" --json",
+    "node scripts/audit-public-acceptance-readiness.mjs --root . --json",
+    "node scripts/audit-continue-preflight.mjs --root . --json",
+    "node scripts/run-validation-profile.mjs --target . --profile lite --json",
+    "cmd /c npm run check:encoding",
+    "node scripts/audit-installed-sync.mjs --root . --installed-root C:\\Users\\Admin\\.codex\\skills\\gse --json",
+    "node scripts/generate-maintenance-snapshot.mjs --root . --target . --installed-root C:\\Users\\Admin\\.codex\\skills\\gse --skip-release-bundle --execute --json",
+    "node scripts/run-gse-command.mjs --root . --target . --command \"/gse close\" --json",
+    "git diff --check"
+  ],
+  "residualRisks": [
+    "supportSliceBoundary is optional metadata and must stay a narrow scope or exit criterion, not a replacement for product-visible progress.",
+    "Existing product projects need future slices to add or infer userVisibleDelta from their real UI/API/provider/export evidence; CP22 still detects repeated internal drift.",
+    "Native slash-command support remains an optional per-host adapter claim and is not claimed without a real host invocation record."
+  ],
+  "riskArchive": [
+    {
+      "archivedAt": "2026-07-10",
+      "risk": "0.1.1 is already published and immutable; release metadata changes must publish a new semver version.",
+      "resolution": "GSE-147 uses 0.1.2 as the publish target."
+    },
+    {
+      "archivedAt": "2026-07-10",
+      "risk": "Session sync records prove notification attempts and honest outcomes, not that another running session adopted the capability immediately.",
+      "resolution": "GSE-146 surfaces compactState.sessionSyncBoundary and CP21 so adoption is false unless an explicit adoption record exists."
+    },
+    {
+      "archivedAt": "2026-07-08",
+      "risk": "The final-form roadmap contract is not itself final-form completion; live claims still come from references/final-readiness.md and audit-final-readiness.mjs.",
+      "resolution": "Preserved through /gse continue blockedGates and final-readiness claim boundary."
+    },
+    {
+      "archivedAt": "2026-07-08",
+      "risk": "The next implementation slice must reduce long prompt dependence through /gse continue hard preflight, not add more prose-only guidance.",
+      "resolution": "Implemented by scripts/generate-continue-packet.mjs and /gse continue routing."
+    },
+    {
+      "archivedAt": "2026-07-08",
+      "risk": "Use /gse doctor and audit-public-acceptance-readiness.mjs as the source of truth for pending final-form public gates.",
+      "resolution": "Integrated into continue packet ownerExternalGateSummary and blockedGates."
+    },
+    {
+      "archivedAt": "2026-07-08",
+      "risk": "The final-form plan could be interpreted as only the remaining owner/external release gates.",
+      "resolution": "references/final-form-roadmap.md now contains Wave 1-5 execution plan and current gap list for local engineering and external evidence."
+    },
+    {
+      "archivedAt": "2026-07-08",
+      "risk": "Project guard automation is the next local engineering gap: repeated real-project lessons must become preflight guard items instead of reminder prose.",
+      "resolution": "Implemented as soft project guard preflight through .gse/project-guards.md, audit-project-guards.mjs, scaffold generation, and /gse continue CP11."
+    },
+    {
+      "archivedAt": "2026-07-08",
+      "risk": "Evidence level granularity still needs sharper UI/browser/API/CI labels.",
+      "resolution": "Implemented through evidenceLevel and requiredEvidenceLevel taxonomy, audit-evidence-levels.mjs, /gse continue CP12, and close gate CG09."
+    },
+    {
+      "archivedAt": "2026-07-08",
+      "risk": "Role and dispatch fallback packets need stronger default output and no-fake-dispatch checks.",
+      "resolution": "Implemented through role-dispatch-fallback.md, role-fallback-packet.md, .gse/agents/role-fallback-packets.md, audit-role-dispatch-fallback.mjs, and /gse continue CP13."
+    },
+    {
+      "archivedAt": "2026-07-08",
+      "risk": "Downgraded evidence is now visible before continue/close, but each project decides whether a downgrade blocks close.",
+      "resolution": "Preserved through evidenceLevel and requiredEvidenceLevel warnings."
+    },
+    {
+      "archivedAt": "2026-07-08",
+      "risk": "Use /gse doctor and audit-public-acceptance-readiness.mjs as the source of truth for current final-form external gates.",
+      "resolution": "Preserved as the public/external acceptance route while state repair handles local state/evidence drift."
+    },
+    {
+      "archivedAt": "2026-07-08",
+      "risk": "State/evidence repair is intentionally conservative: invalid JSON/JSONL is reported with concrete actions, not guessed or overwritten.",
+      "resolution": "GSE-115 implemented /gse repair and CP14; the remaining risk is now bounded as a deliberate repair policy."
+    },
+    {
+      "archivedAt": "2026-07-08",
+      "risk": "Automatic /gse repair writes are limited to reversible residual-risk compaction with .gse/backups; stale next-action drift remains a deliberate update.",
+      "resolution": "GSE-115 verified execute-gated residual-risk compaction and kept stale next-action repair deliberate."
+    },
+    {
+      "archivedAt": "2026-07-08",
+      "risk": "Learning promotion writes candidate-only .gse/learning-promotions.md output; guards, gates, templates, scripts, and skill updates still require deliberate follow-up changes.",
+      "resolution": "GSE-116 implemented candidate-only learning promotion; deliberate follow-up remains as normal slice work rather than an active blocker."
+    },
+    {
+      "archivedAt": "2026-07-08",
+      "risk": "Classification is deterministic and project-generic, not a human semantic review.",
+      "resolution": "GSE-116 bounded classification as routing evidence and preserved human review for actual guard/gate/script mutations."
+    },
+    {
+      "archivedAt": "2026-07-09",
+      "risk": "Role fallback packets prove auditable sequential role boundaries, not real subagent execution.",
+      "resolution": "Preserved by role fallback packets, no-fake-dispatch close gate, and host capability records; no longer needs default active risk display."
+    },
+    {
+      "archivedAt": "2026-07-09",
+      "risk": "AION and MuseFlow drill warnings are project-local readiness signals; GSE behavior must stay project-generic and must not mutate target projects during read-only drills.",
+      "resolution": "Preserved by target hardening drill limits and maintenance cadence; no longer needs default active risk display."
+    },
+    {
+      "archivedAt": "2026-07-09",
+      "risk": "Installed sync evidence proves local source/package/installed-copy parity only at the time of the audit; it does not publish a package or prove host-native slash-command support.",
+      "resolution": "Archived by GSE state repair to keep active residual risks compact."
+    },
+    {
+      "archivedAt": "2026-07-09",
+      "risk": "UI/browser evidence policy proves evidence labeling and downgrade surfacing only; target-project visible UI claims still need real browser or screenshot-backed proof.",
+      "resolution": "Archived by GSE state repair to keep active residual risks compact."
+    },
+    {
+      "archivedAt": "2026-07-09",
+      "risk": "Maintenance snapshots are point-in-time freshness evidence; future capability edits must regenerate the snapshot, release bundle, and installed copy.",
+      "resolution": "Archived by GSE state repair to keep active residual risks compact."
+    }
+  ]
+}

package/CHANGELOG.md

@@ -2,9 +2,49 @@
 
 All notable GSE changes should be recorded here before a public package, catalog entry, or release handoff is marked ready.
 
-## Unreleased
-
-### Added
+## Unreleased
+
+## 0.2.0 - 2026-07-11
+
+### Added
+
+- Product-visible progress drift guard for `/gse continue`, so repeated internal/component slices surface a product-visible recovery candidate before support work self-replicates.
+- Product outcome gate for product projects, requiring a named user-visible delta or an explicitly bounded support slice.
+- Optional `currentSlice.supportSliceBoundary` metadata for deliberate maintenance slices; bounded support slices now surface their exit criterion without weakening `CP22` drift detection.
+- Target hardening drill adoption summaries and repair plans that distinguish GSE core gaps from target-local hygiene.
+
+### Changed
+
+- `/gse repair --execute` guidance is gated behind target worktree ownership before mutating target `.gse` state or evidence.
+- Encoding close checks now use the npm script path and avoid creating dependency artifacts.
+- `validate-gse` now includes the latest target-hardening and product-outcome guard coverage.
+
+### Verified
+
+- `v0.1.2..HEAD` contains the product outcome, product drift, bounded support, target repair ownership, and adoption hygiene slices intended for this minor release.
+- Public registry and GitHub release evidence for `0.1.2` remain accepted; `0.2.0` must receive its own npm/GitHub publication evidence after publish.
+
+### Boundary
+
+- Native host slash-command support remains optional per host adapter and is not claimed without host invocation evidence.
+
+## 0.1.2 - 2026-07-10
+
+### Added
+
+- Public npm/GitHub install metadata for `@t275005746/gse`.
+- README and README.zh-CN npm install quick path.
+
+### Verified
+
+- Public GitHub repository visibility and npm registry status are checked during release close.
+- `/gse continue` exposes session-sync adoption boundaries so installed-copy sync is not mistaken for target-session adoption.
+
+### Boundary
+
+- Native host slash-command support remains optional per host adapter and is not claimed without host invocation evidence.
+
+### Added
 
 - Project bootstrap modes for Lite, Standard, and Enterprise `.gse/` scaffolds.
 - Native Goal-Spec-Evidence operating model with change packs, execution-quality packs, evidence taxonomy, close gates, and target project audits.
@@ -17,8 +57,12 @@ All notable GSE changes should be recorded here before a public package, catalog
 - `validate-gse.mjs` consolidates structural, project bootstrap, adoption, host adapter, compatibility, release, distribution, signing, command, target validation, and lifecycle audits.
 - AION and MuseFlow were used as real long-running target-project validation fixtures for GSE adoption checks.
 
-### Not Yet Accepted
-
-- Public registry publication and marketplace approval are not verified.
-- Host-native slash-command execution is not verified except where a host-specific record explicitly says so.
-- Open-source license selection remains an owner decision and must be recorded before a public release is accepted.
+### Accepted
+
+- Public npm registry publication and GitHub Release evidence are accepted for `@t275005746/gse@0.1.2`.
+- MIT license selection is recorded for the public release.
+
+### Not Claimed
+
+- Host-native slash-command execution is not verified except where a host-specific record explicitly says so.
+- Marketplace approval remains separate from npm/GitHub publication evidence.

package/README.md

@@ -22,12 +22,19 @@ Goal -> Spec -> Execute -> Evidence -> Learn
 - Optional adapters for host folders, LSP notes, MCP notes, hooks, plugins, and project skills
 - Release, packaging, public-collaboration, and evidence-gate workflows for mature projects
 
-## Installation
-
-Use GSE from a checked-out copy:
-
-```bash
-node scripts/validate-gse.mjs --root . --json
+## Installation
+
+Install from npm:
+
+```bash
+npm install -g @t275005746/gse
+gse status --target .
+```
+
+Use GSE from a checked-out copy:
+
+```bash
+node scripts/validate-gse.mjs --root . --json
 ```
 
 Package a checked-out copy for handoff:

package/README.zh-CN.md

@@ -22,12 +22,19 @@ Goal -> Spec -> Execute -> Evidence -> Learn
 - 可选 host folders、LSP、MCP、hooks、plugins、project skills 适配说明
 - 面向成熟项目的 release、packaging、public collaboration 和 evidence gate 工作流
 
-## 安装
-
-从已检出的 GSE 副本直接使用：
-
-```bash
-node scripts/validate-gse.mjs --root . --json
+## 安装
+
+从 npm 安装：
+
+```bash
+npm install -g @t275005746/gse
+gse status --target .
+```
+
+从已检出的 GSE 副本直接使用：
+
+```bash
+node scripts/validate-gse.mjs --root . --json
 ```
 
 把已检出的副本打包给其他环境：

package/SKILL.md

@@ -37,19 +37,32 @@ Default stance: keep the workflow as light as the task allows and as rigorous as
 Portable command helpers:
 
 - Short CLI wrapper: `node <skill>/scripts/gse.mjs status --target <project-root> --json`
-- Short continuation prompt: `node <skill>/scripts/generate-session-prompt.mjs --target <project-root>`
-- Portable command runner: `node <skill>/scripts/run-gse-command.mjs --target <project-root> --command "/gse continue"`
-- Validation profile runner: `node <skill>/scripts/run-validation-profile.mjs --target <project-root> --profile lite|standard|enterprise|release`
+- Short continuation packet: `node <skill>/scripts/generate-continue-packet.mjs --target <project-root>`
+- Portable command runner: `node <skill>/scripts/run-gse-command.mjs --target <project-root> --command "/gse continue"`
+- State/evidence repair doctor: `node <skill>/scripts/run-gse-command.mjs --target <project-root> --command "/gse repair" --json`
+- Direct repair audit: `node <skill>/scripts/audit-state-repair.mjs --target <project-root> --json`
+- Validation profile runner: `node <skill>/scripts/run-validation-profile.mjs --target <project-root> --profile lite|standard|enterprise|release`
 - Command execution audit: `node <skill>/scripts/audit-command-execution.mjs --root <skill> --profile lite|full`
-- Close readiness check: `node <skill>/scripts/audit-close-gate.mjs --target <project-root>`
+- Close readiness check: `node <skill>/scripts/audit-close-gate.mjs --target <project-root>`
+- Project guard preflight: `node <skill>/scripts/audit-project-guards.mjs --target <project-root> --json`
 - GSE owner/external action list: `node <skill>/scripts/run-gse-command.mjs --target <skill> --command "/gse owner-actions" --json --compact`
 - Owner/external live evidence probe: `node <skill>/scripts/run-gse-command.mjs --target <skill> --command "/gse probe --public-repo-url <url>" --json`
 - Release bundle dry-run/write route: `node <skill>/scripts/run-gse-command.mjs --target <skill> --command "/gse release" --json`
 - Package dry-run/write route: `node <skill>/scripts/run-gse-command.mjs --target <skill> --command "/gse package" --json`
 - Install dry-run/write route: `node <skill>/scripts/run-gse-command.mjs --target <skill> --command "/gse install --source <package-dir> --install-target <install-skill-dir>" --json`
 - Public release checklist route: `node <skill>/scripts/run-gse-command.mjs --target <skill> --command "/gse public-release" --json`
-- Learning capture route: `node <skill>/scripts/run-gse-command.mjs --target <project-root> --command "/gse learn --summary <lesson>" --execute --json`
-- Existing project state/index update: `node <skill>/scripts/update-project-state.mjs --target <project-root>`
+- Learning capture route: `node <skill>/scripts/run-gse-command.mjs --target <project-root> --command "/gse learn --summary <lesson>" --execute --json`
+- Learning drift audit: `node <skill>/scripts/audit-learning-drift.mjs --root <skill> --target <project-root> --json`
+- Target hardening drills: `node <skill>/scripts/audit-target-hardening-drills.mjs --root <skill> --aion-target <project-root> --museflow-target <project-root> --json`
+- Maintenance cadence audit: `node <skill>/scripts/audit-maintenance-cadence.mjs --root <skill> --json`
+- Maintenance snapshot: `node <skill>/scripts/generate-maintenance-snapshot.mjs --root <skill> --target <project-root> --installed-root <installed-skill-dir> --execute --json`
+- Installed package smoke: `node <skill>/scripts/generate-maintenance-snapshot.mjs --root <installed-skill-dir> --target <installed-skill-dir> --package-smoke --skip-release-bundle --json`
+- Installed sync audit: `node <skill>/scripts/audit-installed-sync.mjs --root <skill> --installed-root <installed-skill-dir> --json`
+- Session sync record audit: `node <skill>/scripts/audit-session-sync.mjs --root <skill> --json`
+- Conservative evidence-level backfill: `node <skill>/scripts/backfill-evidence-levels.mjs --root <project-root> --json`
+- Historical evidence review queue: `node <skill>/scripts/audit-evidence-review-queue.mjs --root <skill> --target <project-root> --json`
+- UI/browser evidence policy audit: `node <skill>/scripts/audit-ui-browser-evidence-policy.mjs --root <skill> --target <project-root> --json`
+- Existing project state/index update: `node <skill>/scripts/update-project-state.mjs --target <project-root>`
 - Change spec pack: `node <skill>/scripts/init-change.mjs --target <project-root> --change-id <id> --level lite|standard|enterprise`
 - Public release record: `node <skill>/scripts/record-public-release.mjs --root <project-root> --license-status owner-required`
 - Release bundle: `node <skill>/scripts/generate-release-bundle.mjs --root <skill> --label <release-label> --out <bundle-dir>`
@@ -100,8 +113,9 @@ For long-running projects, bind the work to `.gse/goal-map.md` or the project's
 - Project-specific standards and tools: `references/project-profile.md`
 - Project-local agent workspace: `references/project-agent-workspace.md`
 - Host-specific adapters: `references/host-adapters.md`, `references/compatibility.md`
-- Benchmark and gap audit: `references/benchmark-audit.md`
-- Task level selection: `references/task-levels.md`
+- Benchmark and gap audit: `references/benchmark-audit.md`
+- Final form roadmap: `references/final-form-roadmap.md`, `scripts/audit-final-form-roadmap.mjs`
+- Task level selection: `references/task-levels.md`
 - Goal maps: `references/goal-map.md`
 - Specs and change folders: `references/spec-workflow.md`
 - Agent roles and ownership: `references/agent-roles.md`, `references/file-ownership.md`
@@ -128,7 +142,7 @@ For long-running projects, bind the work to `.gse/goal-map.md` or the project's
 - Release owner action plan drill: `scripts/audit-release-owner-action-plan-drill.mjs`
 - Public release checklist: `scripts/generate-public-release-checklist.mjs`, `scripts/audit-public-release-checklist.mjs`
 - Final-form progress report: `scripts/generate-final-form-progress-report.mjs`, `scripts/audit-final-form-progress-report.mjs`
-- Packaging and maintenance: `references/packaging.md`
+- Packaging and maintenance: `references/packaging.md`, `references/maintenance-cadence.md`, `scripts/audit-maintenance-cadence.mjs`, `scripts/generate-maintenance-snapshot.mjs`, `scripts/audit-maintenance-snapshot.mjs`, `scripts/audit-installed-sync.mjs`, `scripts/record-session-sync.mjs`, `scripts/audit-session-sync.mjs`
 - CI readiness: `.github/workflows/validate-gse.yml`, `scripts/audit-ci-readiness.mjs`
 - Public collaboration templates: `.github/PULL_REQUEST_TEMPLATE.md`, `.github/ISSUE_TEMPLATE/`, `scripts/audit-public-collaboration-templates.mjs`
 - Release trust and key custody: `references/release-trust.md`
@@ -142,7 +156,13 @@ For long-running projects, bind the work to `.gse/goal-map.md` or the project's
 - Final acceptance packet: `scripts/generate-final-acceptance-packet.mjs`, `scripts/audit-final-acceptance-packet.mjs`
 - Recovery and handoff: `references/recovery.md`
 - Forward testing: `references/forward-test.md`
-- Learning loop: `references/learning-system.md`
-- Learning capture: `scripts/record-learning.mjs`, `scripts/audit-learning-system.mjs`
-- Drift audit: `references/drift-audit.md`
+- Learning loop: `references/learning-system.md`
+- Learning capture: `scripts/record-learning.mjs`, `scripts/audit-learning-system.mjs`
+- Learning drift: `scripts/audit-learning-drift.mjs`
+- Conservative evidence-level backfill: `scripts/backfill-evidence-levels.mjs`
+- Historical evidence review queue: `scripts/audit-evidence-review-queue.mjs`
+- UI/browser evidence policy: `scripts/audit-ui-browser-evidence-policy.mjs`
+- Target hardening drills: `scripts/audit-target-hardening-drills.mjs`
+- Project guards: `references/project-guards.md`, `scripts/audit-project-guards.mjs`
+- Drift audit: `references/drift-audit.md`
 - Design basis and source boundaries: `references/design-basis.md`

package/assets/templates/dispatch-packet.md

@@ -4,16 +4,21 @@ Use this when assigning work to a real subagent, another human/agent session, or
 
 Do not require this packet for tiny single-agent edits. Use it when delegation, role separation, file ownership, or review evidence matters.
 
-## Execution Mode
-
-- Mode: real-subagent | sequential-role | handoff-session
-- Host/tool used:
-- Tool status: verified | documented | unknown | unavailable
-- If not real-subagent, state fallback reason:
+## Execution Mode
+
+- Mode: real-subagent | sequential-role | handoff-session
+- Real delegation used: yes | no
+- Host/tool used:
+- Tool status: verified | documented | unknown | unavailable
+- If not real-subagent, state fallback reason:
+- Dispatch evidence:
+- Fallback execution:
+- Role output evidence:
+- Claim boundary:
 
 ## Role
 
-- Role: Coordinator | Product Analyst | Architect | Code Locator | Builder | Reviewer | QA | Docs/Evidence | Other:
+- Role: Coordinator | Planner | Product Analyst | Architect | Locator | Implementer | Verifier | Reviewer | QA | Docs/Evidence | Release | Other:
 - Skill focus:
 - Model/tool preference, if project-approved:
 
@@ -75,12 +80,13 @@ Return a concise report with:
 - Residual risks:
 - Questions or blockers:
 
-## Verification
-
-- Required focused test/smoke/check:
-- Acceptable evidence level: result | verified | accepted
-- What proves success:
-- What would fail the task:
+## Verification
+
+- Required focused test/smoke/check:
+- Evidence status: result | verified | accepted
+- Acceptable evidence level: result | verified-unit | verified-component | verified-api | verified-browser | verified-ci | accepted-owner | accepted-release | external-required
+- What proves success:
+- What would fail the task:
 
 ## Stop Conditions
 
@@ -101,4 +107,6 @@ Stop and report `NEEDS_CONTEXT` or `BLOCKED` if:
 
 ## Notes For Sequential Fallback
 
-When no real subagent tool exists, use this packet as a role checklist in the main session. Say that no real delegation occurred if reporting delegation status matters. Keep role boundaries honest.
+When no real subagent tool exists, use this packet as a role checklist in the main session. Say that no real delegation occurred if reporting delegation status matters. Keep role boundaries honest.
+
+For repeatable role fallback packets, use `assets/templates/role-fallback-packet.md` and `references/role-dispatch-fallback.md`.

package/assets/templates/evidence.md

@@ -1,8 +1,14 @@
-# Evidence
-
-## Verification Commands
-
-## Results
+# Evidence
+
+## Status
+
+- Evidence status:
+- Evidence level:
+- Required evidence level:
+
+## Verification Commands
+
+## Results
 
 ## Files Changed