@bendyline/gilde 0.1.39 → 0.1.41

package/data/craftbook-templates/fl/flaky-test-fix/versions/1.0.0/test.json

@@ -0,0 +1,240 @@
+{
+  "schemaVersion": 1,
+  "title": "Deflake an order-dependent test with receipts",
+  "objective": "The craftbook drives a real deflake of a seeded order-dependence flake: statistical reproduction with recorded failing runs, a mechanism-level diagnosis, cleanup at the level every test shares (never skipping or weakening the test), and a stability proof - verified mechanically, including a five-run consecutive-green oracle, a late-probe order-robustness check, and a mutant restoring the original leaking order.",
+  "tags": [
+    "code",
+    "flaky-test",
+    "tests",
+    "tactical-fleet"
+  ],
+  "prompt": "Use the Fix a Flaky Test craftbook: our suite is red in CI but the failing test passes when people run it by itself, so it keeps getting waved through. The report is in source/flake-report.md. Find the nondeterminism, remove it for real, and prove the suite stays green.",
+  "setup": {
+    "projectName": "Flagship Flags",
+    "about": "A tiny feature-flags module and its test suite. Tests run with `npm run test` (node --test).",
+    "files": [
+      {
+        "path": "package.json",
+        "content": "{\n  \"name\": \"flagship\",\n  \"private\": true,\n  \"version\": \"1.0.0\",\n  \"type\": \"module\",\n  \"scripts\": {\n    \"test\": \"node --test\"\n  }\n}\n",
+        "modelInput": false
+      },
+      {
+        "path": "src/flags.js",
+        "content": "const flags = new Map();\n\nexport function enable(name) {\n  flags.set(name, true);\n}\n\nexport function disable(name) {\n  flags.delete(name);\n}\n\nexport function isEnabled(name) {\n  return flags.get(name) === true;\n}\n\nexport function enabledCount() {\n  return flags.size;\n}\n\nexport function resetFlags() {\n  flags.clear();\n}\n"
+      },
+      {
+        "path": "tests/flags.test.mjs",
+        "content": "import assert from 'node:assert/strict';\nimport { test } from 'node:test';\nimport { enable, disable, isEnabled, enabledCount } from '../src/flags.js';\n\ntest('enable turns a flag on', () => {\n  enable('beta-banner');\n  assert.equal(isEnabled('beta-banner'), true);\n});\n\ntest('disable turns a flag off again', () => {\n  enable('holiday-theme');\n  disable('holiday-theme');\n  assert.equal(isEnabled('holiday-theme'), false);\n});\n\ntest('unknown flags read as disabled', () => {\n  assert.equal(isEnabled('dark-mode'), false);\n});\n\ntest('a fresh session starts with no flags enabled', () => {\n  assert.equal(enabledCount(), 0);\n});\n"
+      },
+      {
+        "path": "source/flake-report.md",
+        "content": "# Flake report\n\nThe suite has been red in CI all week, and every developer who ran the failing test by itself saw it pass - so it kept getting waved through.\n\n    npm run test\n    not ok 4 - a fresh session starts with no flags enabled\n      AssertionError: 1 !== 0\n\nRunning the full suite fails on that test consistently; running just that one test with `--test-name-pattern \"fresh session\"` is green every time. Nobody has touched `src/flags.js` in weeks.\n\nConstraints:\n\n- The pristine-session test guards a real invariant (feature sessions must start clean). Do not delete or weaken it.\n- The app depends on `src/flags.js` exactly as it is - fix the tests' hygiene, not the module's API.\n",
+        "modelInput": true
+      },
+      {
+        "path": "tests/verify-deflake.mjs",
+        "content": "import assert from 'node:assert/strict';\nimport { execFileSync } from 'node:child_process';\nimport { cpSync, mkdirSync, readFileSync, readdirSync, rmSync, writeFileSync } from 'node:fs';\nimport { join } from 'node:path';\nimport { enable, isEnabled, resetFlags, enabledCount } from '../src/flags.js';\n\nconst root = process.cwd();\nconst ORACLE_FILE = 'verify-deflake.mjs';\n\n// 1) The flags module still means what it meant.\nresetFlags();\nenable('oracle-probe');\nassert.equal(isEnabled('oracle-probe'), true, 'enable must still work');\nassert.equal(enabledCount(), 1, 'enabledCount must still count');\nresetFlags();\nassert.equal(enabledCount(), 0, 'resetFlags must still clear');\nconsole.log('DEFLAKE_ORACLE flags semantics ok');\n\nfunction runSuite(cwd) {\n  try {\n    execFileSync(process.execPath, ['--test'], { cwd, stdio: 'pipe', timeout: 30000 });\n    return 0;\n  } catch (err) {\n    return typeof err.status === 'number' ? err.status : 1;\n  }\n}\n\nfunction copyTree(dest) {\n  rmSync(dest, { recursive: true, force: true });\n  mkdirSync(dest, { recursive: true });\n  cpSync(join(root, 'src'), join(dest, 'src'), { recursive: true });\n  cpSync(join(root, 'tests'), join(dest, 'tests'), { recursive: true });\n  rmSync(join(dest, 'tests', ORACLE_FILE), { force: true });\n  cpSync(join(root, 'package.json'), join(dest, 'package.json'));\n  return dest;\n}\n\n// 2) Five consecutive green runs of the real suite.\nfor (let run = 1; run <= 5; run += 1) {\n  assert.equal(runSuite(root), 0, `full-suite run ${run} of 5 must be green`);\n}\nconsole.log('DEFLAKE_ORACLE stable 5x');\n\n// 3) The pristine-session assertion survives, unweakened and unskipped.\nconst testFiles = readdirSync(join(root, 'tests')).filter(\n  (name) => name !== ORACLE_FILE && /\\.(mjs|cjs|js)$/.test(name),\n);\nconst combined = testFiles\n  .map((name) => readFileSync(join(root, 'tests', name), 'utf8'))\n  .join('\\n');\nassert.match(\n  combined,\n  /enabledCount\\s*\\(\\s*\\)\\s*(?:,\\s*0|===\\s*0)/,\n  'the pristine-session assertion (enabledCount() must be 0) has to survive',\n);\nassert.ok(\n  !/\\.skip\\s*\\(|\\.todo\\s*\\(|\\.only\\s*\\(|\\{\\s*skip\\s*:|\\{\\s*todo\\s*:/.test(combined),\n  'no test may be skipped, stubbed as todo, or narrowed with only',\n);\nconsole.log('DEFLAKE_ORACLE assertion intact');\n\n// 4) Order robustness: tests appended at the END of the suite must inherit\n// the cleanup. The first probe enables a flag and never cleans up; the\n// second expects a pristine session anyway. Only hygiene that covers every\n// test (beforeEach/afterEach-style) passes both - a one-off reset inside\n// the seeded failing test, or a reorder, fails here. Aliased imports keep\n// the probe valid whatever the model did to the file's own imports.\nconst hostFile = testFiles.find((name) =>\n  /enabledCount/.test(readFileSync(join(root, 'tests', name), 'utf8')),\n);\nassert.ok(hostFile, 'no test file references enabledCount');\nconst probeRoot = copyTree(join(root, '.oracle-probe'));\nconst probeTests =\n  readFileSync(join(probeRoot, 'tests', hostFile), 'utf8') +\n  \"\\n\\nimport { test as zzTest } from 'node:test';\\nimport zzAssert from 'node:assert/strict';\\nimport { enable as zzEnable, isEnabled as zzIsEnabled, enabledCount as zzEnabledCount } from '../src/flags.js';\\n\\nzzTest('zz probe enables a flag of its own', () => {\\n  zzEnable('zz-probe-flag');\\n  zzAssert.equal(zzIsEnabled('zz-probe-flag'), true);\\n});\\n\\nzzTest('zz probe still gets a pristine session', () => {\\n  zzAssert.equal(zzEnabledCount(), 0);\\n});\\n\";\nwriteFileSync(join(probeRoot, 'tests', hostFile), probeTests);\nassert.equal(\n  runSuite(probeRoot),\n  0,\n  'a test appended after the suite must still see a pristine session - cleanup has to cover every test, not only the seeded order',\n);\nconsole.log('DEFLAKE_ORACLE order robust');\n\n// 5) Mutant: restore the ORIGINAL leaking test file - the suite must fail\n// again, proving the seeded defect is still detectable and the green suite\n// comes from removed nondeterminism, not from a neutered module or dodge.\nconst ORIGINAL_TEST_FILE = `import assert from 'node:assert/strict';\nimport { test } from 'node:test';\nimport { enable, disable, isEnabled, enabledCount } from '../src/flags.js';\n\ntest('enable turns a flag on', () => {\n  enable('beta-banner');\n  assert.equal(isEnabled('beta-banner'), true);\n});\n\ntest('disable turns a flag off again', () => {\n  enable('holiday-theme');\n  disable('holiday-theme');\n  assert.equal(isEnabled('holiday-theme'), false);\n});\n\ntest('unknown flags read as disabled', () => {\n  assert.equal(isEnabled('dark-mode'), false);\n});\n\ntest('a fresh session starts with no flags enabled', () => {\n  assert.equal(enabledCount(), 0);\n});\n`;\nconst mutantRoot = copyTree(join(root, '.oracle-mutant'));\nwriteFileSync(join(mutantRoot, 'tests', 'flags.test.mjs'), ORIGINAL_TEST_FILE);\nassert.notEqual(\n  runSuite(mutantRoot),\n  0,\n  'restoring the original leaking order must make the suite fail again - the seeded defect stopped being detectable',\n);\nconsole.log('DEFLAKE_ORACLE mutant caught');\nconsole.log('DEFLAKE_ORACLE done');\n",
+        "surface": "harness"
+      }
+    ],
+    "craftbookParams": {
+      "workPath": "tasks/eval",
+      "scope": "The test 'a fresh session starts with no flags enabled' in tests/flags.test.mjs fails whenever the whole suite runs and passes by itself; see source/flake-report.md. Make the suite deterministic without weakening that test."
+    }
+  },
+  "mocks": [],
+  "success": {
+    "summary": "The order-dependence mechanism is removed with hygiene that covers every test, the pristine-session assertion survives unweakened, five consecutive suite runs are green, a late-appended probe still sees a pristine session, and restoring the original test file makes the suite fail again.",
+    "deliverables": [
+      {
+        "path": "tasks/eval/flake-evidence.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 500,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/flake-evidence.md",
+            "pattern": "^##\\s+Symptom[\\s\\S]*^##\\s+Runs observed[\\s\\S]*^##\\s+Failure signature[\\s\\S]*^##\\s+Suspected class",
+            "flags": "im",
+            "label": "flake-evidence sections in order"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "tasks/eval/flake-evidence.md",
+            "minCitations": 2,
+            "artifact": true
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/diagnosis.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 600,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/diagnosis.md",
+            "pattern": "^##\\s+Mechanism[\\s\\S]*^##\\s+Experiment[\\s\\S]*^##\\s+Defect site[\\s\\S]*^##\\s+Siblings checked",
+            "flags": "im",
+            "label": "diagnosis sections in order"
+          },
+          {
+            "kind": "contains",
+            "file": "tasks/eval/diagnosis.md",
+            "pattern": "tests/flags\\.test\\.mjs|src/flags\\.js",
+            "label": "names the real site of the shared-state hazard"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "tasks/eval/diagnosis.md",
+            "minCitations": 2,
+            "artifact": true
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/fix-notes.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 700,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/fix-notes.md",
+            "pattern": "^##\\s+Problem[\\s\\S]*^##\\s+Change[\\s\\S]*^##\\s+Files touched[\\s\\S]*^##\\s+Regression coverage[\\s\\S]*^##\\s+Risk[\\s\\S]*^##\\s+How to verify",
+            "flags": "im",
+            "label": "fix-notes sections in order"
+          },
+          {
+            "kind": "citationsResolve",
+            "file": "tasks/eval/fix-notes.md",
+            "minCitations": 2,
+            "artifact": true
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/validation.md",
+        "kind": "markdown-notes",
+        "artifact": true,
+        "minBytes": 300,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/validation.md",
+            "pattern": "^##\\s+Runs[\\s\\S]*^##\\s+Result",
+            "flags": "im",
+            "label": "validation sections in order"
+          }
+        ]
+      },
+      {
+        "path": "tasks/eval/review.md",
+        "kind": "markdown-report",
+        "artifact": true,
+        "minBytes": 400,
+        "checks": [
+          {
+            "kind": "contains",
+            "file": "tasks/eval/review.md",
+            "pattern": "Verdict:\\s*(?:PASS|REVISE)",
+            "flags": "i",
+            "label": "explicit reviewer verdict"
+          }
+        ]
+      }
+    ],
+    "checks": [
+      {
+        "kind": "notContains",
+        "file": "tests/flags.test.mjs",
+        "pattern": "\\.skip\\s*\\(|\\.todo\\s*\\(|\\.only\\s*\\(|\\{\\s*skip\\s*:|\\{\\s*todo\\s*:",
+        "label": "the flaky test is not skipped, stubbed, or narrowed"
+      },
+      {
+        "kind": "sourceParses",
+        "file": "tests/flags.test.mjs"
+      },
+      {
+        "kind": "nodeRuns",
+        "file": "tests/flags.test.mjs",
+        "timeoutMs": 30000
+      },
+      {
+        "kind": "nodeScriptPasses",
+        "script": "tests/verify-deflake.mjs",
+        "timeoutMs": 60000,
+        "requiredOutput": [
+          {
+            "pattern": "DEFLAKE_ORACLE flags semantics ok",
+            "label": "the flags module still behaves"
+          },
+          {
+            "pattern": "DEFLAKE_ORACLE stable 5x",
+            "label": "five consecutive green suite runs"
+          },
+          {
+            "pattern": "DEFLAKE_ORACLE assertion intact",
+            "label": "the pristine-session assertion survives unweakened"
+          },
+          {
+            "pattern": "DEFLAKE_ORACLE order robust",
+            "label": "a late-appended test still sees a pristine session"
+          },
+          {
+            "pattern": "DEFLAKE_ORACLE mutant caught",
+            "label": "restoring the original order makes the suite fail again"
+          }
+        ]
+      }
+    ],
+    "taskNotes": {
+      "minBytes": 120,
+      "checks": [
+        {
+          "kind": "contains",
+          "file": "task-notes.md",
+          "pattern": "\\bDONE\\b[\\s\\S]*(npm\\s+run\\s+test|node\\s+--test|consecutive)",
+          "flags": "i",
+          "label": "DONE note cites the stability proof"
+        }
+      ]
+    },
+    "taskGraph": {
+      "requireCraftbookTask": true,
+      "requireTerminalStep": true
+    },
+    "unchangedFixtures": [
+      "package.json",
+      "src/flags.js",
+      "source/flake-report.md"
+    ]
+  },
+  "rubric": {
+    "artifact": {
+      "path": "tasks/eval/fix-notes.md",
+      "kind": "markdown"
+    },
+    "axes": [
+      {
+        "name": "Mechanism-level diagnosis",
+        "description": "The nondeterminism is named as a concrete mechanism (shared module state leaking across tests) and pinned with a real experiment, not guessed from the symptom."
+      },
+      {
+        "name": "No masking",
+        "description": "The flake is removed with cleanup or isolation that covers every test; the flaky test keeps its exact assertion and gains no skip, retry, or widened timeout."
+      },
+      {
+        "name": "Receipt-backed stability",
+        "description": "Stability is proven with consecutive green runs recorded as real receipts, and anything unverified is stated plainly instead of claimed."
+      }
+    ]
+  },
+  "qualityFocus": [
+    "statistical reproduction",
+    "mechanism removal over masking",
+    "consecutive-green receipts"
+  ]
+}

package/data/craftbook-templates/fo/folder-to-audio/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "folder-to-audio",
   "role": "general",
+  "category": "media",
   "name": "Text-to-Speech a Folder",
   "description": "Turn a folder of text files (articles, chapters, notes, markdown) into a set of spoken audio files using text-to-speech, so a reading list becomes a listening list. Scopes the voice, file mapping, and chunking rules FIRST so long inputs do not get truncated or mispronounced, then synthesizes one audio artifact per source file with a consistent voice, then verifies every file was rendered and is audible. The scope-before-synthesize ordering is the point: deciding chunk size, file naming, and a manifest up front is what keeps a batch TTS run complete and re-runnable instead of half-finished.",
   "tags": [

package/data/craftbook-templates/fo/forecast-model/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "forecast-model",
   "role": "general",
+  "category": "research",
   "name": "Simple Forecast / Trend Model",
   "description": "Build a simple, defensible forecast of a time series (revenue, demand, signups, usage) with the assumptions and method stated up front and the projection plus a confidence band as the output. Scopes the series, horizon, method, and assumptions FIRST (so the forecast isn't an unexplained black box), then builds the projection with a baseline and an interval, then reviews it for sanity against history and overfitting. Use this for forecasting a metric, projecting a trend, estimating future demand, a simple time-series projection, or a 'what will this be next quarter' estimate.",
   "tags": [

package/data/craftbook-templates/fo/form-fill-batch/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "form-fill-batch",
   "role": "general",
+  "category": "code-build",
   "name": "Batch-Fill Forms from a Dataset",
   "description": "Automate filling a web or PDF form once per row of an input dataset — registrations, applications, data-entry portals, mail-merge into a form. Scopes the field-to-column mapping and a per-row success signal FIRST, then builds a loop that loads each record, maps it onto the form fields, submits, and records the outcome, then verifies every row was attempted, each submission was confirmed, and failures are logged with the reason. Mapping-before-build is the wisdom: lock the column→field map and the 'submitted OK' signal so the run is idempotent, resumable, and auditable rather than a blind click-through.",
   "tags": [

package/data/craftbook-templates/fo/form-wizard/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "form-wizard",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Multi-Step Form Wizard",
   "description": "Build a single-file multi-step form wizard — a signup, checkout, survey, or onboarding form split across steps with a progress indicator, per-step validation, back/next navigation, and a final review-and-submit. Designs the step flow, fields per step, and validation rules first, then implements stateful navigation that preserves entered data across steps. Wizards break when going back loses data or a step advances with invalid input, so the flow-design phase locks the field-per-step map and validation before any markup.",
   "tags": [

package/data/craftbook-templates/fr/freeze-scope/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "freeze-scope",
   "role": "general",
+  "category": "practice",
   "name": "Freeze Scope",
   "description": "Confine all workspace writes to one directory",
   "tags": [

package/data/craftbook-templates/ga/game-with-screens/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "game-with-screens",
   "role": "project-starter",
+  "category": "code-build",
   "name": "Full Game with Title & Game-Over Screens",
   "description": "Build a complete single-file HTML game with the full screen flow — a title/start screen, the gameplay screen, a game-over screen showing the score, and a restart back to a fresh game — wrapping any core arcade or survival mechanic. Designs the mechanic and the screen-state machine first, a cohesive visual look across all screens, then implements a screen manager so transitions are clean and restart truly resets. Many small models nail gameplay but ship with no start or game-over screen; this archetype makes the screen flow a first-class, gated requirement.",
   "tags": [

package/data/craftbook-templates/gl/glossary-build/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "glossary-build",
   "role": "general",
+  "category": "code-docs",
   "name": "Domain Glossary",
   "description": "Build a consistent, accurate glossary for a domain: a planner sets the domain scope, the term-selection criteria, and the entry template, a researcher gathers the canonical definition and usage for each term with sources, and a copywriter writes the alphabetized glossary with cross-references and consistent entries. The ordering matters because terms picked ad hoc leave gaps and inconsistent entries confuse readers; locking the scope, what makes a term in-scope, and a fixed entry template first guarantees coverage and a uniform, cross-linked glossary. Use this for building a domain or product glossary, a terms/definitions reference, an acronym list, onboarding vocabulary, and 'define all the key terms in X' requests.",
   "tags": [

package/data/craftbook-templates/gr/graphql-api/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "graphql-api",
   "role": "project-starter",
+  "category": "code-data",
   "name": "GraphQL API",
   "description": "Build a GraphQL API with a typed schema (SDL), resolvers, queries, mutations, and input validation. Designs the schema FIRST — types, fields, nullability, query/mutation operations, and the resolver-to-data mapping — because in GraphQL the schema IS the contract, then implements resolvers, then writes operation tests covering each query, mutation, and error. Covers GraphQL schema definition language, resolvers, nullable vs non-null fields, mutations, query arguments, N+1 awareness, and error handling.",
   "tags": [

package/data/craftbook-templates/gr/grpc-service/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "grpc-service",
   "role": "project-starter",
+  "category": "code-data",
   "name": "gRPC Service",
   "description": "Build a gRPC service from a Protocol Buffers contract — define the .proto service and messages, implement the server handlers, and verify with client calls including streaming and status codes. Designs the proto contract FIRST — the service, RPC methods, request/response messages, field numbers, and the streaming kinds — because the .proto is the binding contract across languages, then implements the handlers, then tests unary/streaming calls and gRPC status codes. Covers protobuf service/message definitions, field numbering, unary vs server/client/bidi streaming, gRPC status codes, deadlines, and a client-driven test.",
   "tags": [

package/data/craftbook-templates/ha/handbook-section/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "handbook-section",
   "role": "general",
+  "category": "writing",
   "name": "Team Handbook Section",
   "description": "Write a clear, reference-grade section of a team/company handbook — a policy, process, or how-we-work doc that a new hire can read once and act on correctly. Scopes the policy's intent, audience, and edge cases FIRST, writes unambiguous prose with concrete examples, a quick-reference summary, and FAQ, then has a reviewer check it for ambiguity and contradictions with how things actually work. Use for onboarding docs, policy pages, process documentation, and internal wikis.",
   "tags": [

package/data/craftbook-templates/he/hero-image/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "hero-image",
   "role": "general",
+  "category": "media",
   "name": "Marketing Hero Image",
   "description": "Create a single high-impact marketing hero image from a brief and place it into a working hero section. Lock the brief FIRST — aspect ratio, subject, mood, palette, focal point, and crucially the safe zone where headline and CTA text will overlay — because a beautiful hero that has no room for copy (or whose focal point sits under the button) is useless. Then generate the image to the brief and place it behind real overlaid text to prove it works. Covers hero banners, marketing imagery, landing-page art, website headers, and key visuals.",
   "tags": [

package/data/craftbook-templates/ho/holiday-card-run/manifest.json

@@ -3,6 +3,7 @@
   "kind": "craftbook-template",
   "id": "holiday-card-run",
   "role": "general",
+  "category": "personal",
   "name": "Holiday Card Run",
   "description": "Make the December run a pleasure instead of a panic: sweep the address list while there is still time to fix it, settle the card message, and produce the print-ready card and the address sheet in one sitting. Locks the roster sweep and the message criteria FIRST, then builds the card, then the address sheet, then reports the gaps that still need a human. Use for holiday cards, the annual card run, 'time for the holiday cards', address list cleanup before card season, and the December mailing.",
   "tags": [

package/data/craftbook-templates/ho/hotfix-flow/manifest.json

@@ -3,16 +3,19 @@
   "kind": "craftbook-template",
   "id": "hotfix-flow",
   "role": "maintenance-review",
+  "category": "code-quality",
   "name": "Hotfix Flow",
-  "description": "Drive an expedited production hotfix from red to green: reproduce the live defect with a failing test, apply the smallest safe fix that makes it pass without scope-creeping into a refactor, and verify the fix plus a clean regression check before it ships out-of-band. The ordering is the whole discipline — reproduce FIRST (a failing test that captures the bug is the contract the fix must satisfy), then fix minimally, then verify the new test passes and nothing else broke. Use this for urgent production bugs, expedited patch releases, and out-of-band fixes where speed matters but a regression would be worse than the original bug.",
+  "description": "Stop a live failure with the smallest change that fixes it at the real site: reproduce with the least machinery that demonstrates the failure, patch minimally with the proper repair recorded as follow-up, validate with a rollback path, and pass an enforced review of the blast radius.",
   "tags": [
-    "gallery",
     "hotfix",
     "bug-fix",
     "tdd",
     "release",
     "patch",
-    "regression"
+    "regression",
+    "incident",
+    "minimal-diff",
+    "rollback"
   ],
   "maintainer": {
     "name": "Gezel"