@t275005746/gse 0.1.0 → 0.1.2

package/README.md

@@ -1,6 +1,6 @@
 # GSE
 
-English | [简体中文](README.zh-CN.md)
+English | [简体中文](https://github.com/275005746/gse/blob/main/README.zh-CN.md)
 
 Goal-Spec-Evidence Engineering for long-running agent-assisted software projects.
 
@@ -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

@@ -1,6 +1,6 @@
 # GSE
 
-[English](README.md) | 简体中文
+[English](https://github.com/275005746/gse/blob/main/README.md) | 简体中文
 
 面向长期 agent 辅助软件项目的 Goal-Spec-Evidence Engineering。
 
@@ -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/SECURITY.md

@@ -1,41 +1,41 @@
-# Security Policy
-
-GSE is an agent workflow skill and scaffold. Security reports may involve scripts, generated project files, host adapters, package/install behavior, signing, release trust, or documentation that could cause unsafe claims.
-
-## Supported Scope
-
-Security-relevant areas include:
-
-- Package, install, URL install, manifest integrity, signing, and verification scripts.
-- Generated host adapters and command pointers.
-- Tool permission guidance, MCP/tool routing guidance, and release trust policy.
-- Evidence, logs, and templates that could leak secrets or raw provider payloads.
-- Documentation that could cause agents to bypass owner approval, license decisions, or unsupported host boundaries.
-
-## Reporting
-
-Until a public security contact is chosen, do not publish exploit details in public issues.
-
-Use the project owner's private reporting channel. If no channel exists, record the issue privately in the maintainers' current coordination channel and mark the public release status as blocked until a contact path exists.
-
-Minimum report contents:
-
-- Affected GSE version, release label, or commit.
-- Affected file or generated artifact.
-- Reproduction steps.
-- Impact and likely affected users or hosts.
-- Whether secrets, credentials, private prompts, provider payloads, or user data are involved.
-- Suggested mitigation if known.
-
-## Handling
-
-- Do not claim a fix is verified until a focused reproduction or audit proves the changed behavior.
-- Do not publish a release if signing, package integrity, or owner trust evidence is contradicted.
-- If a public package may be affected, use `references/release-trust.md` and `assets/templates/release-trust-record.md` to record revocation, rotation, and follow-up.
-- If a project-local GSE scaffold is affected, notify the affected project session or maintainer with the exact files and validation commands.
-
-## Current Limits
-
-- No public vulnerability disclosure address has been owner-approved yet.
-- Public marketplace approval and registry publication are not verified.
-- Host-native slash-command support is not verified unless a host-specific invocation record exists.
+# Security Policy
+
+GSE is an agent workflow skill and scaffold. Security reports may involve scripts, generated project files, host adapters, package/install behavior, signing, release trust, or documentation that could cause unsafe claims.
+
+## Supported Scope
+
+Security-relevant areas include:
+
+- Package, install, URL install, manifest integrity, signing, and verification scripts.
+- Generated host adapters and command pointers.
+- Tool permission guidance, MCP/tool routing guidance, and release trust policy.
+- Evidence, logs, and templates that could leak secrets or raw provider payloads.
+- Documentation that could cause agents to bypass owner approval, license decisions, or unsupported host boundaries.
+
+## Reporting
+
+Until a public security contact is chosen, do not publish exploit details in public issues.
+
+Use the project owner's private reporting channel. If no channel exists, record the issue privately in the maintainers' current coordination channel and mark the public release status as blocked until a contact path exists.
+
+Minimum report contents:
+
+- Affected GSE version, release label, or commit.
+- Affected file or generated artifact.
+- Reproduction steps.
+- Impact and likely affected users or hosts.
+- Whether secrets, credentials, private prompts, provider payloads, or user data are involved.
+- Suggested mitigation if known.
+
+## Handling
+
+- Do not claim a fix is verified until a focused reproduction or audit proves the changed behavior.
+- Do not publish a release if signing, package integrity, or owner trust evidence is contradicted.
+- If a public package may be affected, use `references/release-trust.md` and `assets/templates/release-trust-record.md` to record revocation, rotation, and follow-up.
+- If a project-local GSE scaffold is affected, notify the affected project session or maintainer with the exact files and validation commands.
+
+## Current Limits
+
+- No public vulnerability disclosure address has been owner-approved yet.
+- Public marketplace approval and registry publication are not verified.
+- Host-native slash-command support is not verified unless a host-specific invocation record exists.

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/SUPPORT.md

@@ -1,38 +1,38 @@
-# Support
-
-Use this file to decide where to start when GSE behavior is confusing, incomplete, or blocked.
-
-## First Checks
-
-Run:
-
-```text
-node scripts/validate-gse.mjs --root <gse-root> --json
-```
-
-For a target project using GSE, run:
-
-```text
-node scripts/audit-target-project.mjs --target <project-root> --json
-node scripts/generate-session-prompt.mjs --target <project-root>
-node scripts/audit-close-gate.mjs --target <project-root> --json
-```
-
-For package or install issues, run:
-
-```text
-node scripts/audit-distribution.mjs --root <gse-root> --json
-node scripts/audit-remote-distribution.mjs --root <gse-root> --json
-```
-
-## What To Include In A Support Request
-
-- GSE root path or installed package path.
-- Target project path, if any.
-- Command run and the compact JSON summary.
-- Whether the problem is skill usage, project scaffold, package/install, host adapter, release, or evidence gating.
-- Whether optional tools such as OpenSpec, Comet, Superpowers, LSP, browser automation, MCP, or subagents were actually available.
-
-## Community
-
-GateHub (`https://gatehub.top/`) supports GSE development and contributor coordination.
+# Support
+
+Use this file to decide where to start when GSE behavior is confusing, incomplete, or blocked.
+
+## First Checks
+
+Run:
+
+```text
+node scripts/validate-gse.mjs --root <gse-root> --json
+```
+
+For a target project using GSE, run:
+
+```text
+node scripts/audit-target-project.mjs --target <project-root> --json
+node scripts/generate-session-prompt.mjs --target <project-root>
+node scripts/audit-close-gate.mjs --target <project-root> --json
+```
+
+For package or install issues, run:
+
+```text
+node scripts/audit-distribution.mjs --root <gse-root> --json
+node scripts/audit-remote-distribution.mjs --root <gse-root> --json
+```
+
+## What To Include In A Support Request
+
+- GSE root path or installed package path.
+- Target project path, if any.
+- Command run and the compact JSON summary.
+- Whether the problem is skill usage, project scaffold, package/install, host adapter, release, or evidence gating.
+- Whether optional tools such as OpenSpec, Comet, Superpowers, LSP, browser automation, MCP, or subagents were actually available.
+
+## Community
+
+GateHub (`https://gatehub.top/`) supports GSE development and contributor coordination.

package/assets/marketplace/README.md

@@ -1,7 +1,7 @@
-# Marketplace Metadata
-
-This folder contains portable discovery metadata for publishing or listing GSE in a skill, plugin, or agent-workflow catalog.
-
-The metadata is intentionally host-neutral. It describes what GSE is, how to validate it, which entrypoints matter, and which host capabilities still require separate runtime evidence.
-
-Do not add maintainer secrets, local machine paths, private project names, or unverified marketplace approval claims here.
+# Marketplace Metadata
+
+This folder contains portable discovery metadata for publishing or listing GSE in a skill, plugin, or agent-workflow catalog.
+
+The metadata is intentionally host-neutral. It describes what GSE is, how to validate it, which entrypoints matter, and which host capabilities still require separate runtime evidence.
+
+Do not add maintainer secrets, local machine paths, private project names, or unverified marketplace approval claims here.

package/assets/marketplace/gse-listing.json

@@ -1,75 +1,75 @@
-{
-  "schemaVersion": 1,
-  "name": "gse",
-  "displayName": "GSE",
-  "tagline": "Goal-Spec-Evidence Engineering for long-running agentic software projects.",
-  "summary": "Goal-Spec-Evidence workflow skill for AI coding agents that turns ad hoc development into goal maps, scoped specs, focused execution, evidence gates, and reusable learning.",
-  "categories": [
-    "agentic engineering",
-    "software development workflow",
-    "spec-driven development",
-    "AI coding agents",
-    "project governance"
-  ],
-  "keywords": [
-    "GSE",
-    "Goal-Spec-Evidence",
-    "agentic engineering",
-    "spec-driven development",
-    "SDD",
-    "AI coding agent workflow",
-    "evidence gates",
-    "goal map",
-    "project scaffolding",
-    "OpenSpec-style changes",
-    "Superpowers-style execution"
-  ],
-  "hostSupport": [
-    {
-      "host": "Codex-style agents",
-      "status": "documented",
-      "adapter": ".codex/gse-command.md",
-      "notes": "Portable runner and pointer adapter are verified; project-level native slash-command execution is host-specific."
-    },
-    {
-      "host": "Claude Code-style agents",
-      "status": "documented",
-      "adapter": ".claude/commands/gse.md",
-      "notes": "Generated command file shape is verified in fixtures; real host invocation requires host runtime evidence."
-    },
-    {
-      "host": "Custom agent runtimes",
-      "status": "documented",
-      "adapter": "runtime-specific bridge",
-      "notes": "Runtime capabilities should be verified inside the target project before being marked verified."
-    }
-  ],
-  "entrypoints": [
-    "SKILL.md",
-    "package.json",
-    "README.md",
-    "README.zh-CN.md",
-    "scripts/init-project.mjs",
-    "scripts/run-gse-command.mjs",
-    "scripts/validate-gse.mjs",
-    "scripts/audit-npm-package-metadata.mjs",
-    "scripts/audit-npm-tarball-install.mjs"
-  ],
-  "verification": [
-    "node scripts/validate-gse.mjs --root . --json",
-    "node scripts/audit-npm-package-metadata.mjs --root . --json",
-    "node scripts/audit-marketplace-discovery.mjs --root . --json",
-    "node scripts/audit-host-ui-invocation.mjs --root . --json"
-  ],
-  "distribution": {
-    "packageScript": "scripts/package-gse.mjs",
-    "installScript": "scripts/install-gse.mjs",
-    "signingScript": "scripts/sign-gse-package.mjs",
-    "trustPolicy": "references/release-trust.md"
-  },
-  "boundaries": [
-    "GSE is not a hosted service.",
-    "GSE does not require OpenSpec, Superpowers, Comet, MCP, LSP, browser automation, or subagents.",
-    "Marketplace approval, maintainer identity, and native host UI invocation require separate evidence."
-  ]
-}
+{
+  "schemaVersion": 1,
+  "name": "gse",
+  "displayName": "GSE",
+  "tagline": "Goal-Spec-Evidence Engineering for long-running agentic software projects.",
+  "summary": "Goal-Spec-Evidence workflow skill for AI coding agents that turns ad hoc development into goal maps, scoped specs, focused execution, evidence gates, and reusable learning.",
+  "categories": [
+    "agentic engineering",
+    "software development workflow",
+    "spec-driven development",
+    "AI coding agents",
+    "project governance"
+  ],
+  "keywords": [
+    "GSE",
+    "Goal-Spec-Evidence",
+    "agentic engineering",
+    "spec-driven development",
+    "SDD",
+    "AI coding agent workflow",
+    "evidence gates",
+    "goal map",
+    "project scaffolding",
+    "OpenSpec-style changes",
+    "Superpowers-style execution"
+  ],
+  "hostSupport": [
+    {
+      "host": "Codex-style agents",
+      "status": "documented",
+      "adapter": ".codex/gse-command.md",
+      "notes": "Portable runner and pointer adapter are verified; project-level native slash-command execution is host-specific."
+    },
+    {
+      "host": "Claude Code-style agents",
+      "status": "documented",
+      "adapter": ".claude/commands/gse.md",
+      "notes": "Generated command file shape is verified in fixtures; real host invocation requires host runtime evidence."
+    },
+    {
+      "host": "Custom agent runtimes",
+      "status": "documented",
+      "adapter": "runtime-specific bridge",
+      "notes": "Runtime capabilities should be verified inside the target project before being marked verified."
+    }
+  ],
+  "entrypoints": [
+    "SKILL.md",
+    "package.json",
+    "README.md",
+    "README.zh-CN.md",
+    "scripts/init-project.mjs",
+    "scripts/run-gse-command.mjs",
+    "scripts/validate-gse.mjs",
+    "scripts/audit-npm-package-metadata.mjs",
+    "scripts/audit-npm-tarball-install.mjs"
+  ],
+  "verification": [
+    "node scripts/validate-gse.mjs --root . --json",
+    "node scripts/audit-npm-package-metadata.mjs --root . --json",
+    "node scripts/audit-marketplace-discovery.mjs --root . --json",
+    "node scripts/audit-host-ui-invocation.mjs --root . --json"
+  ],
+  "distribution": {
+    "packageScript": "scripts/package-gse.mjs",
+    "installScript": "scripts/install-gse.mjs",
+    "signingScript": "scripts/sign-gse-package.mjs",
+    "trustPolicy": "references/release-trust.md"
+  },
+  "boundaries": [
+    "GSE is not a hosted service.",
+    "GSE does not require OpenSpec, Superpowers, Comet, MCP, LSP, browser automation, or subagents.",
+    "Marketplace approval, maintainer identity, and native host UI invocation require separate evidence."
+  ]
+}

package/assets/templates/acceptance-execution-packet.md

@@ -1,73 +1,73 @@
-# Acceptance Execution Packet
-
-Use this packet when GSE needs external acceptance evidence instead of another structural audit.
-
-Choose exactly one path per packet.
-
-```text
-Acceptance path: fresh-session | owner-approved project write
-Target project or session:
-Purpose:
-Required inputs:
-Allowed files:
-Forbidden files:
-Allowed commands:
-Forbidden commands:
-Expected output:
-Evidence record path:
-Acceptance gate:
-Accepted by:
-Stop conditions:
-Residual risk if incomplete:
-Next action after completion:
-```
-
-## Fresh-Session Path
-
-Use when a separate session, thread, host worker, or equivalent can run the GSE continuation path without hidden conversation history.
-
-Required inputs:
-
-- `SKILL.md`
-- `.gse/gse-design-master-plan.md`
-- `.gse/goal-map.md`
-- `.gse/current-slice.md`
-- `references/forward-test.md`
-- `references/evidence-taxonomy.md`
-
-Acceptance gate: the separate session identifies the current slice, states outcome/scope/acceptance/evidence/risk/next action, runs or describes the smallest valid verification, and records `Accepted by: fresh-session` only if it actually executed the packet.
-
-## Owner-Approved Project Write Path
-
-Use when a target project owner explicitly allows GSE to write project-local `.gse/` adoption or update artifacts.
-
-Required inputs:
-
-- Project owner approval text or issue/task link.
-- Target project rule file such as `AGENTS.md`, `CLAUDE.md`, or README.
-- `references/adoption-recipes.md`
-- `assets/templates/target-adoption-evidence.md`
-- `assets/templates/update-release-acceptance-record.md`
-
-Default allowed files:
-
-- `.gse/README.md`
-- `.gse/project-profile.md`
-- `.gse/goal-map.md`
-- `.gse/quality-gates.md`
-- `.gse/tooling.md`
-- `.gse/evidence/YYYY-MM-DD.md`
-
-Default forbidden files:
-
-- Source code, lockfiles, secrets, generated outputs, screenshots, build artifacts, and unrelated host config.
-
-Acceptance gate: the owner-approved project record exists, project-local verification ran, residual risks are recorded, and the owner or named policy accepts the verified record.
-
-## Anti-Overclaim Rules
-
-- Do not write `Accepted by: fresh-session` unless a separate session actually ran the packet.
-- Do not write `Accepted by: owner` unless owner approval is explicit and recorded.
-- Do not treat a generated packet, local validation, fixture audit, or read-only discovery as acceptance.
-- Do not expand allowed files or commands without updating the packet and recording why.
-- If a stop condition occurs, record `Evidence status: not ready` or `verified` with `Accepted by: not accepted`.
+# Acceptance Execution Packet
+
+Use this packet when GSE needs external acceptance evidence instead of another structural audit.
+
+Choose exactly one path per packet.
+
+```text
+Acceptance path: fresh-session | owner-approved project write
+Target project or session:
+Purpose:
+Required inputs:
+Allowed files:
+Forbidden files:
+Allowed commands:
+Forbidden commands:
+Expected output:
+Evidence record path:
+Acceptance gate:
+Accepted by:
+Stop conditions:
+Residual risk if incomplete:
+Next action after completion:
+```
+
+## Fresh-Session Path
+
+Use when a separate session, thread, host worker, or equivalent can run the GSE continuation path without hidden conversation history.
+
+Required inputs:
+
+- `SKILL.md`
+- `.gse/gse-design-master-plan.md`
+- `.gse/goal-map.md`
+- `.gse/current-slice.md`
+- `references/forward-test.md`
+- `references/evidence-taxonomy.md`
+
+Acceptance gate: the separate session identifies the current slice, states outcome/scope/acceptance/evidence/risk/next action, runs or describes the smallest valid verification, and records `Accepted by: fresh-session` only if it actually executed the packet.
+
+## Owner-Approved Project Write Path
+
+Use when a target project owner explicitly allows GSE to write project-local `.gse/` adoption or update artifacts.
+
+Required inputs:
+
+- Project owner approval text or issue/task link.
+- Target project rule file such as `AGENTS.md`, `CLAUDE.md`, or README.
+- `references/adoption-recipes.md`
+- `assets/templates/target-adoption-evidence.md`
+- `assets/templates/update-release-acceptance-record.md`
+
+Default allowed files:
+
+- `.gse/README.md`
+- `.gse/project-profile.md`
+- `.gse/goal-map.md`
+- `.gse/quality-gates.md`
+- `.gse/tooling.md`
+- `.gse/evidence/YYYY-MM-DD.md`
+
+Default forbidden files:
+
+- Source code, lockfiles, secrets, generated outputs, screenshots, build artifacts, and unrelated host config.
+
+Acceptance gate: the owner-approved project record exists, project-local verification ran, residual risks are recorded, and the owner or named policy accepts the verified record.
+
+## Anti-Overclaim Rules
+
+- Do not write `Accepted by: fresh-session` unless a separate session actually ran the packet.
+- Do not write `Accepted by: owner` unless owner approval is explicit and recorded.
+- Do not treat a generated packet, local validation, fixture audit, or read-only discovery as acceptance.
+- Do not expand allowed files or commands without updating the packet and recording why.
+- If a stop condition occurs, record `Evidence status: not ready` or `verified` with `Accepted by: not accepted`.