@bendyline/gilde 0.1.9 → 0.1.10

package/data/craftbook-templates/in/investigate/manifest.json

@@ -6,7 +6,6 @@
   "description": "Systematic root-cause debugging procedure. Iron Law: no fixes without investigation. Gathers symptoms, reproduces, traces, finds root cause, saves the learning.",
   "tags": [
     "debug",
-    "gstack",
     "memory"
   ],
   "maintainer": {

package/data/craftbook-templates/in/investigate/versions/1.0.0/craftbook.json

@@ -1,7 +1,7 @@
 {
   "id": "investigate",
   "name": "Investigate",
-  "description": "Systematic root-cause debugging procedure. Six steps:\n\n1. **Gather symptoms** — observable signals, no theorizing yet\n2. **Search prior** — has this project seen this before? (memory)\n3. **Reproduce** — deterministic repro before any tracing\n4. **Trace to root cause** — keep asking 'and why is THAT?'\n5. **Propose fix** — state it; don't apply unless asked\n6. **Save learning** — stamp (symptom → root cause → fix) into memory\n\nPorted from gstack's `/investigate`. The principle is the Iron Law:\n**no fixes without investigation**. Jumping to a fix without root cause\neither ships a coincidence (the bug comes back), papers over the real\ncause (introduces tech debt), or fixes a symptom you didn't actually\nunderstand.\n\nWhere gstack used `~/.gstack/projects/{slug}/learnings.jsonl`, this\ncraftbook uses the per-gezel/project memory subsystem. The\n`search-prior.ts` script wraps `search_memory` with the symptom-shape\nquery; `save-learning.ts` wraps `save_memory` with structured metadata\nso future `search-prior` queries find the match.\n\nThe Iron Law is not literal: sometimes a one-line typo fix is the right\nmove. The principle is \"if you can't say *why* this fix works, you're\nguessing.\" The craftbook's structure makes that guessing visible.\n",
+  "description": "Systematic root-cause debugging procedure. Six steps:\n\n1. **Gather symptoms** — observable signals, no theorizing yet\n2. **Search prior** — has this project seen this before? (memory)\n3. **Reproduce** — deterministic repro before any tracing\n4. **Trace to root cause** — keep asking 'and why is THAT?'\n5. **Propose fix** — state it; don't apply unless asked\n6. **Save learning** — stamp (symptom → root cause → fix) into memory\n\nThe principle is the Iron Law:\n**no fixes without investigation**. Jumping to a fix without root cause\neither ships a coincidence (the bug comes back), papers over the real\ncause (introduces tech debt), or fixes a symptom you didn't actually\nunderstand.\n\nWhere the upstream procedure used a per-project `learnings.jsonl` file,\nthis craftbook uses the per-gezel/project memory subsystem. The\n`search-prior.ts` script wraps `search_memory` with the symptom-shape\nquery; `save-learning.ts` wraps `save_memory` with structured metadata\nso future `search-prior` queries find the match.\n\nThe Iron Law is not literal: sometimes a one-line typo fix is the right\nmove. The principle is \"if you can't say *why* this fix works, you're\nguessing.\" The craftbook's structure makes that guessing visible.\n",
   "entryStepId": "gather-symptoms",
   "triggers": [
     "investigate this",

package/data/craftbook-templates/in/investigate/versions/1.1.0/craftbook.json

@@ -1,7 +1,7 @@
 {
   "id": "investigate",
   "name": "Investigate",
-  "description": "Systematic root-cause debugging procedure. Six steps:\n\n1. **Gather symptoms** — observable signals, no theorizing yet\n2. **Search prior** — has this project seen this before? (memory)\n3. **Reproduce** — deterministic repro before any tracing\n4. **Trace to root cause** — keep asking 'and why is THAT?'\n5. **Propose fix** — state it; don't apply unless asked\n6. **Save learning** — stamp (symptom → root cause → fix) into memory\n\nPorted from gstack's `/investigate`. The principle is the Iron Law:\n**no fixes without investigation**. Jumping to a fix without root cause\neither ships a coincidence (the bug comes back), papers over the real\ncause (introduces tech debt), or fixes a symptom you didn't actually\nunderstand.\n\nWhere gstack used `~/.gstack/projects/{slug}/learnings.jsonl`, this\ncraftbook uses the per-gezel/project memory subsystem. The\n`search-prior.ts` script wraps `search_memory` with the symptom-shape\nquery; `save-learning.ts` wraps `save_memory` with structured metadata\nso future `search-prior` queries find the match.\n\nThe Iron Law is not literal: sometimes a one-line typo fix is the right\nmove. The principle is \"if you can't say *why* this fix works, you're\nguessing.\" The craftbook's structure makes that guessing visible.\n",
+  "description": "Systematic root-cause debugging procedure. Six steps:\n\n1. **Gather symptoms** — observable signals, no theorizing yet\n2. **Search prior** — has this project seen this before? (memory)\n3. **Reproduce** — deterministic repro before any tracing\n4. **Trace to root cause** — keep asking 'and why is THAT?'\n5. **Propose fix** — state it; don't apply unless asked\n6. **Save learning** — stamp (symptom → root cause → fix) into memory\n\nThe principle is the Iron Law:\n**no fixes without investigation**. Jumping to a fix without root cause\neither ships a coincidence (the bug comes back), papers over the real\ncause (introduces tech debt), or fixes a symptom you didn't actually\nunderstand.\n\nWhere the upstream procedure used a per-project `learnings.jsonl` file,\nthis craftbook uses the per-gezel/project memory subsystem. The\n`search-prior.ts` script wraps `search_memory` with the symptom-shape\nquery; `save-learning.ts` wraps `save_memory` with structured metadata\nso future `search-prior` queries find the match.\n\nThe Iron Law is not literal: sometimes a one-line typo fix is the right\nmove. The principle is \"if you can't say *why* this fix works, you're\nguessing.\" The craftbook's structure makes that guessing visible.\n",
   "entryStepId": "gather-symptoms",
   "triggers": [
     "investigate this",