@zalom/plastic 1.0.0-alpha.7 → 1.0.0-alpha.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zalom/plastic",
-  "version": "1.0.0-alpha.7",
+  "version": "1.0.0-alpha.9",
   "description": "Intent-driven idea development system for AI coding agents",
   "type": "module",
   "bin": {

package/scripts/doctor.rb

@@ -681,6 +681,49 @@ def check_project_stores
       )
     end
 
+    # project_yml_exists
+    project_yml_path = File.join(PLASTIC_HOME, "projects", slug, "project.yml")
+    project_yml_data = nil
+
+    if File.exist?(project_yml_path)
+      checks << check(
+        category: "project_stores", name: "project_yml_exists", status: "pass",
+        message: "project.yml exists for project '#{slug}'"
+      )
+      project_yml_data = load_yaml_safe(project_yml_path)
+    else
+      checks << check(
+        category: "project_stores", name: "project_yml_exists", status: "warn",
+        message: "project.yml missing for project '#{slug}'",
+        fixable: true, fix_hint: "Create project.yml from template — see plastic:creating-project"
+      )
+    end
+
+    # governing_docs_exist
+    if project_yml_data.is_a?(Hash) && project_yml_data["governing_docs"].is_a?(Array) && !project_yml_data["governing_docs"].empty?
+      project_path = project_info.is_a?(Hash) ? project_info["path"] : nil
+
+      if project_path
+        missing_docs = project_yml_data["governing_docs"].reject do |doc_path|
+          File.exist?(File.join(project_path, doc_path))
+        end
+
+        if missing_docs.empty?
+          checks << check(
+            category: "project_stores", name: "governing_docs_exist", status: "pass",
+            message: "All governing docs exist for project '#{slug}'"
+          )
+        else
+          checks << check(
+            category: "project_stores", name: "governing_docs_exist", status: "warn",
+            message: "#{missing_docs.size} governing doc(s) missing for project '#{slug}'",
+            details: missing_docs,
+            fixable: false
+          )
+        end
+      end
+    end
+
     # cross_references — if project has `parent` field, check global store intent tags
     parent_id = project_info.is_a?(Hash) ? project_info["parent"] : nil
     next unless parent_id

package/scripts/install.rb

@@ -217,6 +217,31 @@ def bootstrap
   puts "  \u{2705} Store bootstrapped"
 end
 
+def bootstrap_project_store(slug)
+  project_dir = File.join(PLASTIC_HOME, "projects", slug)
+  store_dir = File.join(project_dir, "store")
+
+  FileUtils.mkdir_p(store_dir)
+
+  template = File.join(PACKAGE_ROOT, "templates", "project.yml")
+  dest = File.join(project_dir, "project.yml")
+  write_if_missing(dest, File.read(template)) if File.exist?(template)
+
+  write_if_missing(File.join(project_dir, "INDEX.md"), <<~MD)
+    # Index
+
+    ## Active
+
+    ## Future
+
+    ## Clusters
+
+    ## Abandoned
+
+    ## Completed
+  MD
+end
+
 # --- Agent adapters ---
 
 def install_for_agent(key, force)

package/scripts/lib/bridge.rb

@@ -2,6 +2,7 @@
 # encoding: UTF-8
 
 require "json"
+require "yaml"
 require "fileutils"
 require "tempfile"
 
@@ -136,4 +137,37 @@ module Bridge
 
     nil # no gate violation
   end
+
+  PROJECT_CONFIG_DEFAULTS = {
+    "governing_docs" => ["AGENTS.md"],
+    "release" => {
+      "on_complete" => "commit",
+    },
+  }.freeze
+
+  def self.read_project_config(slug)
+    path = File.join(Dir.home, ".plastic", "projects", slug, "project.yml")
+    config = if File.exist?(path)
+               YAML.safe_load(File.read(path)) || {}
+             else
+               {}
+             end
+
+    deep_merge(PROJECT_CONFIG_DEFAULTS, config)
+  rescue => e
+    $stderr.puts "Warning: failed to read project config for #{slug}: #{e.message}"
+    PROJECT_CONFIG_DEFAULTS.dup
+  end
+
+  def self.deep_merge(base, overlay)
+    result = base.dup
+    overlay.each do |key, value|
+      if value.is_a?(Hash) && result[key].is_a?(Hash)
+        result[key] = deep_merge(result[key], value)
+      else
+        result[key] = value
+      end
+    end
+    result
+  end
 end

package/skills/auto/SKILL.md

@@ -111,12 +111,26 @@ During initial project creation, all decisions are non-destructive by definition
 1. Verify all checklist items are checked
 2. Write `outcome.md` with detailed results
 3. Write `## Outcome` summary in the intent file (1-2 sentences)
-4. Review `## Insights` for observations that should spawn future intents. If any:
+4. **Release (if configured)**
+   1. Detect project — match CWD against paths in `~/.plastic/projects.yml` to find the project slug. If no match, skip to step 5 (default commit-only behavior).
+   2. Read `~/.plastic/projects/{slug}/project.yml`. If the file doesn't exist or has no `release` key, skip to step 5.
+   3. Based on `release.on_complete`:
+      - `commit` — git add + commit (same as default, proceed to step 5)
+      - `commit_and_push` — git add + commit + push
+      - `manual` — skip auto-commit, notify user: "Release configured as manual — commit when ready."
+   4. If `release.verify` is set, run the verify command (e.g. `bundle exec rake test`):
+      - **Exit 0 (green):** proceed to sub-step 5
+      - **Non-zero (red):** check `release.on_red`:
+        - `fix_and_retry` — attempt to fix the failure, re-run verify (max 2 retries)
+        - `stop` — write `savepoint.md` with current state, notify user: "Verify failed — savepoint written.", **STOP**
+        - `manual` — notify user: "Verify failed: [summary]. Resolve manually."
+   5. If `release.on_green` has items, invoke `plastic:releasing` to handle them (tag, changelog, publish, etc.). Do NOT duplicate release logic — delegate entirely.
+5. Review `## Insights` for observations that should spawn future intents. If any:
    - Create them (using `plastic:creating-intent` conventions)
    - Update `chain` in the current intent's frontmatter
-5. Move intent from `## Active` to `## Completed` in INDEX.md (with today's date)
-6. Auto-commit: `cd <store-root> && git add . && git commit -m "feat: deliver intent <ID> — <name>"`
-7. Notify user: "Intent [ID] — [name] delivered. [1-2 sentence summary]. See outcome.md for details."
+6. Move intent from `## Active` to `## Completed` in INDEX.md (with today's date)
+7. Auto-commit: `cd <store-root> && git add . && git commit -m "feat: deliver intent <ID> — <name>"`
+8. Notify user: "Intent [ID] — [name] delivered. [1-2 sentence summary]. See outcome.md for details."
 
 ## Error Handling
 

package/skills/releasing/SKILL.md

@@ -6,25 +6,62 @@ description: Use when merging a feature branch to main and tagging a release, bu
 # Releasing
 
 Merge, bump, tag, push. Annotated tags with changelogs. Semantic versioning.
+Project configuration drives the workflow — no hardcoded assumptions.
 
 ## Checklist
 
-- [ ] All tests pass
+- [ ] Read project config
+- [ ] All tests pass (or verification skipped per config)
 - [ ] Merge feature branch to main
-- [ ] Bump version in plugin.json and marketplace.json
+- [ ] Bump version in configured version files
 - [ ] Commit version bump
 - [ ] Create annotated tag
 - [ ] Push to remote with tags
+- [ ] Run post-push actions (GitHub release, npm publish, etc.)
+- [ ] Complete active intent
 
 ## Workflow
 
+### 0. Read Project Config
+
+Before anything else, determine which project we are releasing and load its config.
+
+1. Read `~/.plastic/projects.yml` — find the project whose `path` matches the current working directory.
+2. Extract the project slug (the key under `projects:`).
+3. Read `~/.plastic/projects/{slug}/project.yml` — this contains the `release:` section.
+
+Expected `release:` keys in project.yml:
+
+```yaml
+release:
+  verify: "bin/rails test"              # command to run before release
+  version_file: package.json            # single file containing the version
+  version_files:                        # multiple files (overrides version_file)
+    - package.json
+    - .claude-plugin/plugin.json
+  tag_format: "v{{version}}"            # tag naming pattern ({{version}} is replaced)
+  on_green:                             # actions to run after push succeeds
+    - github_release
+    - npm_publish
+  on_complete: commit_and_push          # what to do with the version bump commit
+  on_red: stop                          # what to do if verification fails
+```
+
+**Fallback:** If no project.yml exists or it has no `release:` section, fall back to asking the user for each step — verify command, version files, tag format, and post-push actions.
+
 ### 1. Verify Tests Pass
 
+Run the verification command from `release.verify` in project.yml:
+
 ```bash
-ruby test/read_config_test.rb && ruby test/config_template_test.rb
+# Example: release.verify = "ruby -Itest test/*_test.rb"
+<verify-command-from-config>
 ```
 
-All tests must pass before release. Do not proceed if any fail.
+- If `release.verify` is present: run it. All checks must pass before proceeding.
+- If `release.verify` is absent or empty: skip verification. Log that no verify command is configured.
+- If `release.on_red` is `stop`: abort the release on failure.
+- If `release.on_red` is `fix_and_retry`: ask the user to fix and re-run.
 
 ### 2. Determine Version Bump
 
@@ -47,18 +84,26 @@ Always `--no-ff` to preserve branch history in the merge commit.
 
 ### 4. Bump Version
 
-Update ALL THREE files — they must stay in sync:
-- `package.json` → `"version": "X.Y.Z"`
-- `.claude-plugin/plugin.json` → `"version": "X.Y.Z"`
-- `.claude-plugin/marketplace.json` → `"version": "X.Y.Z"`
+Determine which files to update from project.yml:
+
+- If `release.version_files` is set: update ALL listed files (they must stay in sync).
+- Else if `release.version_file` is set: update that single file.
+- Else: ask the user which files contain the version.
+
+Update the version string in each file, then commit:
 
 ```bash
-git add package.json .claude-plugin/plugin.json .claude-plugin/marketplace.json
+git add <version-files>
 git commit -m "chore: bump version to X.Y.Z — [one-line summary]"
 ```
 
 ### 5. Create Annotated Tag
 
+Read `release.tag_format` from project.yml to determine the tag name:
+
+- If set (e.g. `"v{{version}}"`): replace `{{version}}` with the new version string.
+- If not set: default to `vX.Y.Z`.
+
 Generate the changelog from commits since the last tag:
 
 ```bash
@@ -68,7 +113,7 @@ git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges | grep -E
 Create the tag with a multi-line message:
 
 ```bash
-git tag -a vX.Y.Z -m "vX.Y.Z — [release name]
+git tag -a <tag-name> -m "<tag-name> — [release name]
 
 - [changelog bullet points from feat/fix/refactor commits]"
 ```
@@ -79,16 +124,42 @@ git tag -a vX.Y.Z -m "vX.Y.Z — [release name]
 git push origin main --tags
 ```
 
-### 7. GitHub Release
+### 7. Post-Push Actions
+
+Read `release.on_green` from project.yml. This is a list of actions to run after a successful push. Execute each in order:
 
-Create a GitHub release from the tag. Use `--generate-notes` to auto-generate changelog from commits since the previous tag:
+#### `github_release`
+
+Create a GitHub release from the tag:
 
 ```bash
-gh release create vX.Y.Z --title "vX.Y.Z — [release name]" --generate-notes --notes-start-tag <previous-tag>
+gh release create <tag-name> --title "<tag-name> — [release name]" --generate-notes --notes-start-tag <previous-tag>
 ```
 
 For the first release (no previous tag), write notes manually with `--notes "..."` instead.
 
+#### `npm_publish`
+
+Publish the package to npm:
+
+```bash
+# For pre-release versions (0.x.y, or version contains -alpha/-beta/-rc):
+npm publish --access public --tag alpha
+
+# For stable versions (>= 1.0.0, no pre-release suffix):
+npm publish --access public
+```
+
+#### Other values
+
+If `on_green` contains an action not listed above, log it:
+
+```
+[releasing] Action "<action>" is configured but not yet implemented. Skipping.
+```
+
+If `on_green` is empty or absent: skip post-push actions entirely.
+
 ### 8. Complete Active Intent
 
 A release IS a delivery. The active intent that drove this work must be completed as part of the release process. This is NOT optional.
@@ -100,17 +171,17 @@ A release IS a delivery. The active intent that drove this work must be complete
    c. Update `## Insights` with final observations
    d. Move from `## Active` to `## Completed` in INDEX.md (with today's date)
    e. Update clusters to show `_(completed)_`
-3. Auto-commit: `cd ~/.plastic && git add . && git commit -m "feat: complete intent <ID> — delivered in v<X.Y.Z>"`
+3. Auto-commit: `cd ~/.plastic && git add . && git commit -m "feat: complete intent <ID> — delivered in <tag-name>"`
 
 **If no active intent exists for this release**, that itself is a problem — work happened outside the intent system. Log it and move on, but flag it.
 
 ## Conventions
 
 - **Annotated tags only** — `git tag -a`, never lightweight tags
-- **Tag format** — `vX.Y.Z` (lowercase v prefix)
-- **Tag message** — first line: `vX.Y.Z — [short name]`, then blank line, then bullet changelog
+- **Tag format** — driven by `release.tag_format` in project.yml (default: `vX.Y.Z`)
+- **Tag message** — first line: `<tag> — [short name]`, then blank line, then bullet changelog
 - **Commit prefixes** — `feat:`, `fix:`, `refactor:`, `chore:`, `docs:` (conventional commits)
-- **Version files** — package.json, plugin.json, and marketplace.json always match
+- **Version files** — driven by project.yml; all listed files must always match
 - **Branch cleanup** — delete merged feature branches: `git branch -d <branch>`
 
 ## Retroactive Tagging

package/templates/project.yml

@@ -0,0 +1,5 @@
+governing_docs:
+  - AGENTS.md
+
+release:
+  on_complete: commit