Feature/release start 0.3.1

.changeset/README.md

@@ -16,15 +16,15 @@ Follow the prompts to select version bump type and describe your changes.
 2. **Version PR** — CI opens/updates a "Version Packages" PR when changesets merge to main
 3. **Release** — Merging the Version PR triggers npm publish and GitHub Release
 
-> **Note:** Contributors only need to run `pnpm changeset`. Versioning (`changeset version`) and publishing happen automatically in CI.
+> **Note:** Contributors only need to run `pnpm changeset`. Versioning and publishing are run via the manual release workflow (`release-prepare`) or local manual release script.
 
 ## Template
 
 Use this structure for your changeset content:
 
 ```markdown
 ---
-"@fission-ai/openspec": patch
+"@augmenter-dev/lightspec": patch
 ---
 
 ### New Features

.changeset/config.json

@@ -2,7 +2,7 @@
   "$schema": "https://unpkg.com/@changesets/config/schema.json",
   "changelog": [
     "@changesets/changelog-github",
-    { "repo": "Fission-AI/OpenSpec" }
+    { "repo": "augmenter-dev/lightspec" }
   ],
   "commit": false,
   "fixed": [],

.changeset/thin-pigs-stare.md

@@ -0,0 +1,5 @@
+---
+"lightspec": patch
+---
+
+Minor CI updates

.claude/skills/lightspec-apply/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: lightspec-apply
+description: Get instructions for implementing a change
+disable-model-invocation: true
+---
+
+Generate enriched instructions for implementing the tasks in a change.
+
+## Usage
+
+Use this skill when ready to implement the tasks for a change.
+
+## What This Does
+
+1. Shows which artifacts are complete and which are pending
+2. Displays task progress with checkboxes
+3. Provides context files to read
+4. Gives implementation instructions
+5. Shows what's blocking progress (if anything)
+
+## Implementation
+
+Use the CLI command:
+```bash
+lightspec instructions apply [options]
+```
+
+### Options
+
+- `--change <id>`: Change name (auto-detected if only one change)
+- `--schema <name>`: Schema override (auto-detected from change metadata)
+- `--json`: Output as JSON (for agents/automation)
+
+### Example
+
+```bash
+# Get apply instructions for the current change
+lightspec instructions apply
+
+# Get apply instructions for a specific change
+lightspec instructions apply --change add-user-authentication
+
+# Get JSON output for automation
+lightspec instructions apply --json
+```
+
+## Output Interpretation
+
+The command shows:
+- **Progress**: X/Y tasks complete
+- **State**: ready (all artifacts complete), blocked (missing artifacts), or all_done (all tasks complete)
+- **Context Files**: List of artifacts to read for context
+- **Tasks**: Checklist with [x] for done, [ ] for pending
+- **Instruction**: Implementation guidance
+
+## When Blocked
+
+If the state is "blocked", create missing artifacts first using the lightspec-new skill for each artifact, or run `lightspec new change <name>` to continue.

.claude/skills/lightspec-archive/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: lightspec-archive
+description: Archive a completed change and update main specs
+disable-model-invocation: true
+---
+
+Archive a completed change, merging delta specs into main specifications.
+
+## Usage
+
+Use this skill when:
+- A change is fully implemented
+- All tasks are complete
+- Tests pass
+- Ready to integrate changes into main specs
+
+## What This Does
+
+1. Validates the change (unless --no-validate)
+2. Merges delta specs from the change into main specs
+3. Moves the change to the archive
+4. Updates spec versions
+
+## Implementation
+
+Use the CLI command:
+```bash
+lightspec archive [change-name] [options]
+```
+
+### Options
+
+- `-y, --yes`: Skip confirmation prompts
+- `--skip-specs`: Skip spec update (for infrastructure/tooling/doc-only changes)
+- `--no-validate`: Skip validation (not recommended, requires confirmation)
+
+### Example
+
+```bash
+# Archive with prompts
+lightspec archive add-user-authentication
+
+# Archive without confirmation
+lightspec archive add-user-authentication -y
+
+# Archive infrastructure change (no spec updates)
+lightspec archive upgrade-dependencies --skip-specs -y
+```
+
+## Before Archiving
+
+Ensure:
+1. All code changes are committed
+2. Tests pass
+3. Artifacts are complete (check with `lightspec status`)
+4. Delta specs are properly written
+
+## After Archiving
+
+The change will be moved to `lightspec/changes/archive/` and main specs will be updated with the changes.

.claude/skills/lightspec-new/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: lightspec-new
+description: Create a new change proposal for tracking work
+disable-model-invocation: true
+---
+
+Create a new change proposal to track development work.
+
+## Usage
+
+Use this skill when starting a new feature, bug fix, or any tracked work.
+
+## What This Does
+
+1. Creates a new change directory under `lightspec/changes/<name>/`
+2. Creates change metadata for tracking
+3. Optionally adds a README.md with description
+
+## Implementation
+
+Use the CLI command:
+```bash
+lightspec new change <name> [options]
+```
+
+### Options
+
+- `--description <text>`: Description to add to README.md
+- `--schema <name>`: Workflow schema to use (default: spec-driven)
+
+### Example
+
+```bash
+# Create a new change
+lightspec new change add-user-authentication --description "Add OAuth2 authentication"
+
+# Or use default description
+lightspec new change refactor-database
+```
+
+This creates the change structure and makes it ready for artifact creation.

.devcontainer/README.md

@@ -1,6 +1,6 @@
 # Dev Container Setup
 
-This directory contains the VS Code dev container configuration for OpenSpec development.
+This directory contains the VS Code dev container configuration for LightSpec development.
 
 ## What's Included
 

.devcontainer/devcontainer.json

@@ -1,5 +1,5 @@
 {
-  "name": "OpenSpec Development",
+  "name": "LightSpec Development",
   "image": "mcr.microsoft.com/devcontainers/typescript-node:1-20-bookworm",
 
   // Additional tools and features

.github/CODEOWNERS

@@ -1,2 +1,3 @@
 # Default code ownership
-* @TabishB
+* @viteinfinite
+* jlnquere

.github/workflows/ci.yml

@@ -52,8 +52,6 @@ jobs:
 
       - name: Setup pnpm
         uses: pnpm/action-setup@v4
-        with:
-          version: 9
 
       - name: Setup Node.js
         uses: actions/setup-node@v4
@@ -108,8 +106,6 @@ jobs:
 
       - name: Setup pnpm
         uses: pnpm/action-setup@v4
-        with:
-          version: 9
 
       - name: Setup Node.js
         uses: actions/setup-node@v4
@@ -147,8 +143,6 @@ jobs:
 
       - name: Setup pnpm
         uses: pnpm/action-setup@v4
-        with:
-          version: 9
 
       - name: Setup Node.js
         uses: actions/setup-node@v4
@@ -204,16 +198,16 @@ jobs:
             echo "Error: Nix build output 'result' symlink not found"
             exit 1
           fi
-          if [ ! -f "result/bin/openspec" ]; then
-            echo "Error: openspec binary not found in build output"
+          if [ ! -f "result/bin/lightspec" ]; then
+            echo "Error: lightspec binary not found in build output"
             exit 1
           fi
           echo "✅ Build output verified"
 
       - name: Test binary execution
         run: |
           VERSION=$(nix run . -- --version)
-          echo "OpenSpec version: $VERSION"
+          echo "LightSpec version: $VERSION"
           if [ -z "$VERSION" ]; then
             echo "Error: Version command returned empty output"
             exit 1
@@ -251,8 +245,6 @@ jobs:
 
       - name: Setup pnpm
         uses: pnpm/action-setup@v4
-        with:
-          version: 9
 
       - name: Setup Node.js
         uses: actions/setup-node@v4

.github/workflows/polish-release-notes.yml

@@ -19,12 +19,24 @@ permissions:
 jobs:
   polish:
     # Only run on the main repo, not forks
-    if: github.repository == 'Fission-AI/OpenSpec'
+    if: github.repository == 'augmenter-dev/lightspec'
     runs-on: ubuntu-latest
 
     steps:
       - uses: actions/checkout@v4
 
+      - name: Check Claude auth availability
+        id: auth-check
+        env:
+          CLAUDE_CODE_OAUTH_TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
+        run: |
+          if [ -n "${CLAUDE_CODE_OAUTH_TOKEN}" ] || [ -n "${ANTHROPIC_API_KEY}" ]; then
+            echo "has_auth=true" >> "$GITHUB_OUTPUT"
+          else
+            echo "has_auth=false" >> "$GITHUB_OUTPUT"
+          fi
+
       - name: Get current release body
         id: get-release
         env:
@@ -34,18 +46,20 @@ jobs:
           echo "Fetched release notes for ${{ env.TAG_NAME }}"
 
       - name: Transform release notes with Claude
+        if: ${{ steps.auth-check.outputs.has_auth == 'true' }}
         uses: anthropics/claude-code-action@v1
         id: claude
         with:
           claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
           github_token: ${{ secrets.GITHUB_TOKEN }}
           claude_args: "--allowedTools Write,Read"
           prompt: |
-            Transform the changelog in `current-notes.md` into release notes for OpenSpec ${{ env.TAG_NAME }}.
+            Transform the changelog in `current-notes.md` into release notes for LightSpec ${{ env.TAG_NAME }}.
 
             ## Voice
 
-            OpenSpec is a developer tool. Write like you're talking to a peer:
+            LightSpec is a developer tool. Write like you're talking to a peer:
             - Direct and practical, not marketing copy
             - Focus on what changed and why it matters
             - Skip the hype, keep it real
@@ -62,7 +76,7 @@ jobs:
             ```
 
             Examples:
-            - `v0.18.0 - OPSX Experimental Workflow`
+            - `v0.23.0 - Enhanced Change Management`
             - `v0.16.0 - Antigravity, iFlow Support`
             - `v0.15.0 - Gemini CLI, RooCode`
 
@@ -96,7 +110,7 @@ jobs:
 
             ## Rules
 
-            1. Write for developers using OpenSpec with AI coding assistants
+            1. Write for developers using LightSpec with AI coding assistants
             2. Remove commit hashes (like `eb152eb:`), PR numbers, and changesets wrappers (`### Minor Changes`)
             3. Lead with what users can do, not implementation details
             4. One to two sentences per item, max
@@ -109,25 +123,30 @@ jobs:
             Before:
             ```
             ### Minor Changes
-            - 8dfd824: Add OPSX experimental workflow commands and enhanced artifact system
+            - 8dfd824: Add support for archiving completed changes with metadata preservation
               **New Commands:**
-              - `/opsx:ff` - Fast-forward through artifact creation
+              - `lightspec archive` - Archive completed changes
             ```
 
             After (polished-notes.md):
             ```
             ### New
 
-            - **Fast-forward mode** - Generate all planning artifacts at once with `/opsx:ff`. Useful when you already know what you're building.
+            - **Change archiving** - Archive completed changes with `lightspec archive`. Preserves change history and metadata.
             ```
 
             After (release-title.txt):
             ```
-            v0.18.0 - OPSX Experimental Workflow
+            v0.23.0 - Enhanced Change Management
             ```
 
             Write both files. No other output.
 
+      - name: Skip polishing (Claude auth not configured)
+        if: ${{ steps.auth-check.outputs.has_auth != 'true' }}
+        run: |
+          echo "Skipping AI polishing: configure CLAUDE_CODE_OAUTH_TOKEN or ANTHROPIC_API_KEY to enable this step."
+
       - name: Update release
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}