@zalom/plastic 1.14.1 → 2.0.0-alpha.10

package/skills/store-indexing/evals/evals.json

@@ -1,22 +0,0 @@
-{
-  "skill_name": "plastic-store-indexing",
-  "notes": "Intent 66a. Spec for the QMD-first step when locating a specific intent to reclassify/flag/cluster before grep/Read. Runner is intent 76; spec only.",
-  "evals": [
-    {
-      "id": 1,
-      "scope": "behavior",
-      "set": "validation",
-      "prompt": "QMD is present. The user says: move the intent about the statusline into the Completed section.",
-      "expected_output": "When locating one specific intent rather than rebuilding every section, before scanning the store with grep/Read runs `ruby ~/.plastic/scripts/qmd-sync search \"statusline\"` to surface the candidate intent, then opens the authoritative intent file for the hit it reclassifies. No-op fallback to the directory scan when QMD is absent.",
-      "files": [],
-      "assertions": [
-        {
-          "type": "human",
-          "check": "qmd-sync search is run before the directory scan when locating a specific intent; authoritative file opened for the hit",
-          "observed": "SKILL.md (or agent file) carries the QMD-first step: run qmd-sync search before grep/Read, then open the authoritative file; no-op fallback when QMD is absent",
-          "result": "pass"
-        }
-      ]
-    }
-  ]
-}

package/skills/store-indexing/references/zettelkasten-linking.md

@@ -1,32 +0,0 @@
-# Zettelkasten Linking Reference
-
-## Three Structural Layers
-
-1. **Content notes** — individual intents (`~/.plastic/store/ID--slug/ID--slug.md`)
-2. **Structure notes** — INDEX.md clusters that organize related intents
-3. **Main structure note** — INDEX.md itself, the top-level entry point
-
-## Three Connection Types (Ranked)
-
-1. **Direct links** (strongest): wikilinks in the `## Links` section, the projection of the
-   frontmatter graph. Each entry is `- [[id--slug|<target's full intent: text>]]` (cross-store:
-   `- [[store:id--slug|...]]`), a clickable `id--slug` target labeled with the target's full
-   `intent:` text. Ordering is mandatory: all `sources` first (top), then all `chain`,
-   frontmatter order preserved within each group. Sources never appear at the end. No
-   source/chain tags, no sub-grouping.
-2. **Sources/Chain** (knowledge graph): `sources` = direct ascendants this was created from (formation, acyclic, must-load); `chain` = forward continuations and related successors (may cycle, lighter context). See [`how-plastic-sources-and-chains-intents.md`](https://github.com/zalom/plastic/blob/main/docs/concepts/how-plastic-sources-and-chains-intents.md) for the full model.
-3. **Tags** (weakest) — shared tags, `project-<name>` for project membership
-
-## When to Create a Cluster
-
-A cluster is a structure note heading. Create one when:
-- 3+ intents share a topic but aren't grouped
-- You notice a pattern across intents
-- A topic area is growing and needs an entry point
-
-## Principles
-
-- Links are the primary organizational mechanism, not folders
-- Structure is a lens, not a container — intents remain first-class citizens
-- Clusters are manually curated, not auto-generated
-- Facts are invalidated, never deleted — completed intents stay in INDEX.md

package/skills/store-provisioning/SKILL.md

@@ -1,55 +0,0 @@
----
-name: plastic-store-provisioning
-description: >-
-  Add an intent store to a project that is already registered in projects.yml
-  but has no store on disk. Use when a project is registered but has no store,
-  when you need to provision a store, or when doctor reports a missing project
-  store (project_store_dir). Thin wrapper around provision-project-store plus an
-  optional qmd register step.
-user-invocable: false
----
-
-# Add a Project Store
-
-Provision the intent store for a project that is already registered in
-`projects.yml` but whose `~/.plastic/projects/{slug}/store/` is missing. This is
-the standalone path; `plastic-project-creating` provisions the store for brand
-new projects.
-
-The provisioner is the single source of truth for store creation. It is pure
-filesystem and idempotent, so re-running is always safe. The project must already
-be registered (this skill does not edit `projects.yml`).
-
-## 1. Resolve the slug
-
-The slug is the project's key under `projects` in `~/.plastic/projects.yml`. If
-the user names a project, map it to its slug. If the slug is missing from
-`projects.yml`, stop: the provisioner requires the project to already be
-registered. If ambiguous, list the registered slugs and ask which one.
-
-## 2. Run the provisioner
-
-```bash
-ruby ~/.plastic/scripts/provision-project-store <slug>
-```
-
-This creates `~/.plastic/projects/<slug>/store/` with `.gitkeep`, writes
-`INDEX.md` and `project.yml` only if they are missing, and never clobbers
-existing files. An unregistered slug exits non-zero with a clear error and
-creates nothing.
-
-## 3. Register with QMD (separate, optional step)
-
-```bash
-ruby ~/.plastic/scripts/qmd-sync register --store ~/.plastic/projects/<slug>/store
-```
-
-This is the only qmd mutation; the provisioner itself performs none. It no-ops
-when qmd is absent, so it is safe to run unconditionally.
-
-## Scope
-
-- Provisioning and qmd registration are two distinct steps. Do not fold qmd into
-  the provisioner.
-- No `projects.yml` edits, no project-tree edits, no tactical-mirror or
-  founding-intent seeding.