@t275005746/gse 0.1.0 → 0.1.1

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`.

package/assets/templates/adr.md

@@ -1,14 +1,14 @@
-# ADR-0000: Title
-
-## Status
-
-Proposed
-
-## Context
-
-## Decision
-
-## Consequences
-
-## Alternatives Considered
-
+# ADR-0000: Title
+
+## Status
+
+Proposed
+
+## Context
+
+## Decision
+
+## Consequences
+
+## Alternatives Considered
+

package/assets/templates/change-brief.md

@@ -1,16 +1,16 @@
-# Change Brief
-
-## Outcome
-
-## Scope
-
-## Non-goals
-
-## Acceptance
-
-## Evidence Plan
-
-## Risks
-
-## Next Action
-
+# Change Brief
+
+## Outcome
+
+## Scope
+
+## Non-goals
+
+## Acceptance
+
+## Evidence Plan
+
+## Risks
+
+## Next Action
+

package/assets/templates/design.md

@@ -1,18 +1,18 @@
-# Design
-
-## Approach
-
-## State / Data Flow
-
-## Interfaces And Contracts
-
-## Permissions And Privacy
-
-## Error And Recovery
-
-## Alternatives Considered
-
-## Rollback
-
-## Open Questions
-
+# Design
+
+## Approach
+
+## State / Data Flow
+
+## Interfaces And Contracts
+
+## Permissions And Privacy
+
+## Error And Recovery
+
+## Alternatives Considered
+
+## Rollback
+
+## Open Questions
+

package/assets/templates/dispatch-packet.md

@@ -1,104 +1,104 @@
-# Dispatch Packet
-
-Use this when assigning work to a real subagent, another human/agent session, or a sequential role simulation in the main session.
-
-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:
-
-## Role
-
-- Role: Coordinator | Product Analyst | Architect | Code Locator | Builder | Reviewer | QA | Docs/Evidence | Other:
-- Skill focus:
-- Model/tool preference, if project-approved:
-
-## Objective
-
-- Outcome:
-- Scope:
-- Non-goals:
-- User-visible impact:
-
-## Required Context
-
-Read these first:
-
-1.
-2.
-3.
-
-Do not read:
-
-- Generated outputs:
-- Historical logs:
-- Unrelated modules:
-
-Known assumptions:
-
-- Verified facts:
-- Design judgments:
-- Open questions:
-
-## File Ownership
-
-- Allowed files:
-- Forbidden files:
-- Read-only files:
-- Shared files requiring coordinator review:
-- Pre-existing dirty files:
-- Release condition:
-
-Follow `references/file-ownership.md`. Do not overwrite user or unrelated agent changes.
-
-## Task Instructions
-
-- Steps to perform:
-- Existing patterns to follow:
-- Constraints:
-- Performance/security/accessibility/privacy notes:
-
-## Expected Output
-
-Return a concise report with:
-
-- Status: DONE | DONE_WITH_CONCERNS | NEEDS_CONTEXT | BLOCKED
-- Files inspected:
-- Files changed:
-- Summary of work:
-- Verification run:
-- Evidence produced:
-- 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:
-
-## Stop Conditions
-
-Stop and report `NEEDS_CONTEXT` or `BLOCKED` if:
-
-- Required context is missing or contradictory.
-- Allowed files are insufficient for the requested change.
-- Target files contain unrelated dirty changes that make merging unsafe.
-- A tool claimed by the packet is unavailable.
-- The task requires broader architecture or product judgment than assigned.
-
-## Review Requirements
-
-- Spec compliance review required: yes | no
-- Code quality review required: yes | no
-- QA/evidence review required: yes | no
-- Coordinator integration required: yes | no
-
-## 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.
+# Dispatch Packet
+
+Use this when assigning work to a real subagent, another human/agent session, or a sequential role simulation in the main session.
+
+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:
+
+## Role
+
+- Role: Coordinator | Product Analyst | Architect | Code Locator | Builder | Reviewer | QA | Docs/Evidence | Other:
+- Skill focus:
+- Model/tool preference, if project-approved:
+
+## Objective
+
+- Outcome:
+- Scope:
+- Non-goals:
+- User-visible impact:
+
+## Required Context
+
+Read these first:
+
+1.
+2.
+3.
+
+Do not read:
+
+- Generated outputs:
+- Historical logs:
+- Unrelated modules:
+
+Known assumptions:
+
+- Verified facts:
+- Design judgments:
+- Open questions:
+
+## File Ownership
+
+- Allowed files:
+- Forbidden files:
+- Read-only files:
+- Shared files requiring coordinator review:
+- Pre-existing dirty files:
+- Release condition:
+
+Follow `references/file-ownership.md`. Do not overwrite user or unrelated agent changes.
+
+## Task Instructions
+
+- Steps to perform:
+- Existing patterns to follow:
+- Constraints:
+- Performance/security/accessibility/privacy notes:
+
+## Expected Output
+
+Return a concise report with:
+
+- Status: DONE | DONE_WITH_CONCERNS | NEEDS_CONTEXT | BLOCKED
+- Files inspected:
+- Files changed:
+- Summary of work:
+- Verification run:
+- Evidence produced:
+- 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:
+
+## Stop Conditions
+
+Stop and report `NEEDS_CONTEXT` or `BLOCKED` if:
+
+- Required context is missing or contradictory.
+- Allowed files are insufficient for the requested change.
+- Target files contain unrelated dirty changes that make merging unsafe.
+- A tool claimed by the packet is unavailable.
+- The task requires broader architecture or product judgment than assigned.
+
+## Review Requirements
+
+- Spec compliance review required: yes | no
+- Code quality review required: yes | no
+- QA/evidence review required: yes | no
+- Coordinator integration required: yes | no
+
+## 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.

package/assets/templates/evidence.md

@@ -1,14 +1,14 @@
-# Evidence
-
-## Verification Commands
-
-## Results
-
-## Files Changed
-
-## User-Visible Outcome
-
-## Residual Risk
-
-## Follow-up
-
+# Evidence
+
+## Verification Commands
+
+## Results
+
+## Files Changed
+
+## User-Visible Outcome
+
+## Residual Risk
+
+## Follow-up
+