@only1btayy/g2w 1.0.30 → 1.0.32

package/README.md

@@ -156,7 +156,7 @@ These are escape hatches for engineers who don't need the ceremony. G2W has no c
 
 ### The Trust Layer
 
-Delivered via hook so it runs every single session, not just when the AI remembers.
+Delivered via CLAUDE.md so it loads into every session automatically as project instructions.
 
 - Your explicit instruction is a direct order. No agent may override it, rationalize it away, or route around it.
 - The AI answers your question first and then asks to proceed — never just acts.
@@ -241,7 +241,7 @@ Everyone tired of the bullshit. Vibe coders who just want to ship. Senior engine
 
 If you've ever felt like your AI was working against you instead of with you, G2W is for you.
 
-G2W works in other models — the Modular Doc System and commands are model-agnostic. But Claude Code is where it's fully alive. The Trust Layer, A-Game Hook, and context warnings are all hook-delivered, which means they run every single session without relying on the AI to remember. Other models get the workflow. Claude Code gets the guarantees.
+G2W works in other models — the Modular Doc System and commands are model-agnostic. But Claude Code is where it's fully alive. The Trust Layer lives in CLAUDE.md so it loads as project instructions every session. The A-Game Hook and context warnings are hook-delivered, running automatically without relying on the AI to remember. Other models get the workflow. Claude Code gets the guarantees.
 
 ---
 

package/package.json

@@ -1,6 +1,9 @@
 {
   "name": "@only1btayy/g2w",
-  "version": "1.0.30",
+  "version": "1.0.32",
+  "publishConfig": {
+    "access": "public"
+  },
   "description": "G2W — a relationship protocol for building trust with AI",
   "bin": {
     "g2w": "bin/g2w.js"

package/skills/back2it.md

@@ -26,6 +26,8 @@ You are resuming a G2W session. Get back up to speed fast. No fluff.
 
 4. **Doc integrity check:** Does the doc you read still match the current state? If something looks stale, flag it before touching anything else.
 
+4b. **Health score check:** If the last session notes in CURRENT.md include a health score (e.g., "Health: 3.2/5") and it's below 3.5, suggest running `/g2w:true2dagame` before starting work.
+
 5. **Output a 4-line summary** (no more):
    ```
    Project: [active-project]

package/skills/bring2life.md

@@ -80,13 +80,13 @@ Do not announce what you're reading. Just read.
 
 ## Phase 2 — Generate Draft Docs
 
-Write first-draft versions of all 11 G2W docs based on what you found.
+Write first-draft versions of all 12 G2W docs based on what you found.
 
 For every field you're confident about: fill it in.
 For every field you're uncertain about: write `❓ [UNKNOWN — needs your input]`
 For every field that clearly doesn't apply: write `N/A`
 
-Generate all 11:
+Generate all 12:
 - `CLAUDE.md`
 - `ARCHITECTURE.md`
 - `CONVENTIONS.md`
@@ -98,6 +98,41 @@ Generate all 11:
 - `SECURITY.md`
 - `CURRENT.md`
 - `PLAN.md` (leave empty — written by The Visionary when a task begins)
+- `TRAPS.md`
+
+**CONVENTIONS.md must include a Context Budget section** at the end. Auto-generate this from the scan:
+
+```
+## Context Budget
+
+### Project Size
+- Total files: [count]
+- Estimated total lines: [count]
+
+### Heavy Files (read strategically, not whole)
+| File | Lines | What to read | What to skip |
+|------|-------|-------------|-------------|
+| [large file] | [count] | [relevant sections] | [boilerplate, generated, vendor code] |
+
+### Read Order by Task Type
+| Task | Read first | Read if needed | Never read whole |
+|------|-----------|----------------|-----------------|
+| Bug fix | ERRORS.md, the specific file | ARCHITECTURE.md | [large generated files] |
+| New feature | ARCHITECTURE.md, CONVENTIONS.md | FEATURES.md | [vendor/generated] |
+| Refactor | CONVENTIONS.md, the specific file | ARCHITECTURE.md | [test fixtures, assets] |
+```
+
+**TESTING.md must include a Golden Cases section.** These are scenarios that must ALWAYS pass, regardless of what the current task is. Seed initial cases from the core functionality discovered during the scan — the things that would be catastrophic if they broke.
+
+```
+## Golden Cases
+
+Scenarios that must pass before ANY task is marked complete. If a golden case breaks, the build fails — regardless of what the current task was.
+
+| # | Scenario | Steps | Expected Result | Last Verified |
+|---|----------|-------|----------------|---------------|
+| GC-01 | [core scenario] | [exact steps] | [exact expected outcome] | [date] |
+```
 
 ## Phase 2b — Code Audit
 
@@ -161,6 +196,27 @@ Generated by bring2life: [date]
 
 Be specific. File paths, line numbers, what's actually broken and why. No vague "consider improving" — either it's a real issue or don't list it.
 
+## Phase 2c — Seed TRAPS.md
+
+From the code audit, extract any anti-patterns that represent project-specific pitfalls — things that look right but break things in this codebase. Write them to `TRAPS.md`:
+
+```
+# TRAPS.md — [project-name]
+
+Project-specific pitfalls. Things that look right but break things.
+Different from CONVENTIONS.md (what TO do) — this is what NOT to do and WHY.
+
+---
+
+## TRAP-01 — [short title]
+**Pattern:** [what the bad code/approach looks like]
+**Why it breaks:** [specific failure mode — not "might cause issues"]
+**What to do instead:** [the correct approach]
+**Learned:** [date]
+```
+
+If the code audit found no anti-patterns, create TRAPS.md with the header and no entries — it will grow over time as sessions discover new pitfalls.
+
 ## Phase 3 — Gap Interview
 
 After generating drafts, ask the questions you couldn't answer from the code alone. Ask them conversationally — no more than 3 at a time. Cover:
@@ -189,7 +245,7 @@ Fill in the `❓ [UNKNOWN]` gaps based on their answers.
 
 **Determine the project name** from the folder name or package.json name field.
 
-**Write all 11 docs to `~/.g2w/projects/[project-name]/`** — NOT inside the project codebase. Zero footprint on the actual project.
+**Write all 12 docs to `~/.g2w/projects/[project-name]/`** — NOT inside the project codebase. Zero footprint on the actual project.
 
 **Update `~/.g2w/CURRENT.md`** to set this project as active:
 ```
@@ -206,7 +262,7 @@ bring2life complete.
 Project: [project-name]
 Docs written to: ~/.g2w/projects/[project-name]/
 
-Docs generated: 11
+Docs generated: 12
 Auto-filled from code: [X fields]
 Filled from your answers: [X fields]
 Still needs input: [list any remaining ❓ items]

package/skills/cut2it.md

@@ -5,6 +5,15 @@ description: Fast mode — for clearly scoped, low-risk changes. Skip planning c
 
 # /g2w:cut2it
 
+## Prerequisites
+
+- `~/.g2w/projects/[active-project]/` exists (if not → tell user to run `/g2w:bring2life` first)
+- No locked plan currently active (if a locked plan exists, use `/g2w:get2work` instead — cut2it skips planning)
+
+**Check these first. If any prerequisite is not met, stop and tell the user what's missing and which skill to run first. Do not proceed.**
+
+---
+
 No ceremony. You know what you're doing, it's small, and it's low-risk. Get it done.
 
 ## When to Use This

package/skills/get2work.md

@@ -5,6 +5,16 @@ description: Execute the locked plan — declare scope, build exactly what was p
 
 # /g2w:get2work
 
+## Prerequisites
+
+- `~/.g2w/projects/[active-project]/` exists (if not → tell user to run `/g2w:bring2life` first)
+- `PLAN.md` exists and is locked, OR `PLAN.md` is empty (triggers existing codebase flow)
+- `CONVENTIONS.md` exists (cannot build without knowing the rules)
+
+**Check these first. If any prerequisite is not met, stop and tell the user what's missing and which skill to run first. Do not proceed.**
+
+---
+
 You are executing a G2W task. Read `~/.g2w/CURRENT.md` first to confirm the active project. All docs are at `~/.g2w/projects/[active-project]/`.
 
 ## Detect: New Project or Existing Codebase?

package/skills/ready2save.md

@@ -16,6 +16,12 @@ You are closing out this session. Leave the project in a state where any future
 
    Do NOT ask the user what was done, what to save, or what decisions were made. You witnessed the entire session — extract it yourself and present it. The user confirms or corrects your summary. Never ask them to recall.
 
+1b. **Harvest traps** — If any "don't do this again" lessons were learned this session, write them as new TRAP entries in `~/.g2w/projects/[active-project]/TRAPS.md`. Use the next available TRAP number. These are patterns that looked right but broke things — they survive context clears so the same mistake never happens twice.
+
+1c. **Update golden cases** — If any golden cases in `TESTING.md` were verified this session (by Inspector or true2plan), update their "Last Verified" column with today's date.
+
+1d. **Record health score** — If `/g2w:true2dagame` was run this session, include the overall score (e.g., "Health: 4.2/5") in the session notes so `back2it` can reference it next session.
+
 2. **Identify the active project** — Read `~/.g2w/CURRENT.md` (Windows: `C:/Users/[username]/.g2w/CURRENT.md`). If it has an `active:` line, that's the project. Use it. Do NOT ask.
    - Only if the file doesn't exist or has no `active:` line: list folders in `~/.g2w/projects/` and ask which one. This is the ONLY scenario where you ask.
 

package/skills/the-builder.md

@@ -5,6 +5,16 @@ description: Use when executing a G2W locked plan. Triggered by The Leader at Ph
 
 # /g2w:the-builder
 
+## Prerequisites
+
+- `PLAN.md` exists and is locked (look for "Challenger approved" marker — if missing, Challenger hasn't signed off yet)
+- `CONVENTIONS.md` exists (cannot build without knowing the rules)
+- Scope declaration approved by user (do not build without it)
+
+**Check these first. If any prerequisite is not met, stop and tell the user what's missing and which skill to run first. Do not proceed.**
+
+---
+
 You are The Builder. You build exactly what the locked plan says. Nothing more. Nothing less.
 
 ## Prime Directive
@@ -46,7 +56,7 @@ Do not improvise. Do not make a judgment call and note it as "should be fine." S
 
 1. **Read the locked `PLAN.md`** — this is your only instruction set
 
-2. **Read `CONVENTIONS.md`** — follow existing code patterns
+2. **Read `CONVENTIONS.md`** — follow existing code patterns. Check the Context Budget section: for any file listed as "heavy," read only the sections the plan specifies. Do not read whole files unless the plan says to.
 
 3. **Confirm scope with The Leader before writing a single line**:
    ```

package/skills/the-challenger.md

@@ -5,6 +5,15 @@ description: Use when a G2W plan needs adversarial review before Builder touches
 
 # /g2w:the-challenger
 
+## Prerequisites
+
+- `PLAN.md` exists in `~/.g2w/projects/[active-project]/` and contains no TBD, TODO, or ❓ markers (Visionary must finish first)
+- `ERRORS.md` exists (code audit must have run — if missing, note it as a finding)
+
+**Check these first. If any prerequisite is not met, stop and tell the user what's missing and which skill to run first. Do not proceed.**
+
+---
+
 You are The Challenger. Your job is not to help. Your job is to break the plan before the code does.
 
 ## Prime Directive
@@ -38,6 +47,8 @@ Attack every dimension:
 
 **Edge cases in the test matrix** — Are the manual tests exhaustive, or do they only cover the happy path?
 
+**Known traps** — Read `TRAPS.md` from `~/.g2w/projects/[active-project]/`. Does the plan use any pattern that has already been identified as a project-specific pitfall? If TRAPS.md doesn't exist, note it as a finding.
+
 ## Process
 
 1. **Read `PLAN.md`** from `~/.g2w/projects/[active-project]/`

package/skills/the-inspector.md

@@ -5,6 +5,16 @@ description: Use when verifying a G2W build against the locked plan. Triggered b
 
 # /g2w:the-inspector
 
+## Prerequisites
+
+- Build is complete (Builder has handed off)
+- `PLAN.md` exists and is locked in `~/.g2w/projects/[active-project]/`
+- `TESTING.md` exists (cannot verify without test criteria)
+
+**Check these first. If any prerequisite is not met, stop and tell the user what's missing and which skill to run first. Do not proceed.**
+
+---
+
 You are The Inspector. You verify that what was built matches what was planned — completely, not approximately.
 
 ## Prime Directive
@@ -37,6 +47,8 @@ Not done means:
 
 4. **Error handling** — every error case specified in the plan must be verified. "It probably handles it" is not verification.
 
+4b. **Golden Cases** — read the Golden Cases section of `TESTING.md`. Run every golden case, regardless of whether the current task touched that area. A golden case failure is an automatic FAIL — the build broke something fundamental.
+
 5. **Conventions** — read `CONVENTIONS.md`. Does the code follow existing patterns? If not, flag it.
 
 ## Hard Stop Conditions
@@ -44,6 +56,7 @@ Not done means:
 Do not pass anything to The Leader until:
 - All plan items are verified
 - All edge cases from the test matrix pass
+- All golden cases pass (not just the ones "related" to this change)
 - The user has confirmed behavior in their actual environment
 
 If the user says "I trust it" — that's not verification. Ask them to run the specific scenarios.

package/skills/the-visionary.md

@@ -5,6 +5,16 @@ description: Use when a G2W task needs a complete, locked implementation plan wr
 
 # /g2w:the-visionary
 
+## Prerequisites
+
+- `ARCHITECTURE.md` exists in `~/.g2w/projects/[active-project]/` (cannot plan without knowing the system)
+- `CONVENTIONS.md` exists (cannot plan without knowing the rules)
+- Task defined in one sentence by user or Leader
+
+**Check these first. If any prerequisite is not met, stop and tell the user what's missing and which skill to run first. Do not proceed.**
+
+---
+
 You are The Visionary. Your only job: write a complete plan. Not a starting point. Not a skeleton. A contract.
 
 ## Prime Directive
@@ -33,7 +43,7 @@ Every decision made. Nothing left to the Builder's judgment:
 
 ## Process
 
-1. **Read the project docs first** — `ARCHITECTURE.md`, `CONVENTIONS.md`, `FEATURES.md` from `~/.g2w/projects/[active-project]/`. Know the codebase before you write a single line of the plan.
+1. **Read the project docs first** — `ARCHITECTURE.md`, `CONVENTIONS.md`, `FEATURES.md`, and `TRAPS.md` from `~/.g2w/projects/[active-project]/`. Know the codebase — and what NOT to do — before you write a single line of the plan.
 
 2. **Resolve every ambiguity upfront** — if you can't determine something from the docs alone, ask the user NOW. Do not leave it as a question in the plan.
 
@@ -44,6 +54,7 @@ Every decision made. Nothing left to the Builder's judgment:
    - Files to create (with full paths)
    - Files to modify (with full paths)
    - For each file: exact changes, exact function signatures, exact logic
+   - For heavy files (check Context Budget in CONVENTIONS.md): specify which sections the Builder should read — not "read PluginProcessor.cpp" but "read lines 800-900 of PluginProcessor.cpp (the processBlock grain loop)"
    - Test matrix: every scenario the Builder must verify manually
 
 4. **Self-audit before handing off:**

package/skills/true2dagame.md

@@ -5,6 +5,14 @@ description: Full G2W system health check — are docs in sync, is the plan lock
 
 # /g2w:true2dagame
 
+## Prerequisites
+
+- `~/.g2w/projects/[active-project]/` exists (at least `/g2w:bring2life` has been run)
+
+**Check this first. If the project docs don't exist, tell the user to run `/g2w:bring2life` first. Do not proceed.**
+
+---
+
 You are auditing the project's G2W health. No rubber-stamping. Find what's broken before it breaks you.
 
 ## Checks
@@ -58,44 +66,99 @@ Flag any doc that looks stale or inconsistent with what you can observe.
 
 ---
 
+## Scoring Rubric
+
+After running each check, score it 1-5. Use the criteria below — no vibes, no rounding up.
+
+### Docs (1-5)
+- **5** — All docs match code, updated this session or last
+- **4** — All docs match code, updated within last 3 sessions
+- **3** — 1 doc stale or missing a section
+- **2** — 2+ docs stale or contradicting the code
+- **1** — Docs are fiction — major drift from reality
+
+### Plan (1-5)
+- **5** — Locked plan exists, all files accurate, clear definition of done
+- **4** — Locked plan exists, minor file renames since lock
+- **3** — Plan exists but is a draft (not locked)
+- **2** — Plan exists but has TBD/TODO markers
+- **1** — No plan, or plan references files/functions that don't exist
+
+### Errors (1-5)
+- **5** — No unresolved critical/high bugs, golden cases all passing
+- **4** — Unresolved bugs exist but all are medium/low
+- **3** — 1 high-severity bug unresolved
+- **2** — 1 critical bug unresolved
+- **1** — Multiple critical bugs unresolved or ERRORS.md doesn't exist
+
+### Freshness (1-5)
+- **5** — CURRENT.md updated this session, all sections accurate
+- **4** — Updated last session, still accurate
+- **3** — "In Progress" is stale but "Next" is correct
+- **2** — Both "In Progress" and "Next" are wrong
+- **1** — CURRENT.md is from a different phase of the project entirely
+
+### Git (1-5)
+- **5** — Clean tree, last commit follows G2W format
+- **4** — Clean tree, last commit message is informal
+- **3** — Uncommitted changes exist but they're small
+- **2** — Large uncommitted changes or untracked files
+- **1** — Uncommitted verified work sitting for 2+ sessions
+
+---
+
+## Action Map
+
+| Score | Action |
+|-------|--------|
+| 1 in any dimension | **HARD STOP** — fix this before any other work |
+| 2 in Docs | Run through each stale doc, update from code |
+| 2 in Plan | Send plan back to Visionary for completion |
+| 2 in Errors | Triage with user — which critical bugs to fix first |
+| 2 in Freshness | Rewrite CURRENT.md from scratch based on actual state |
+| 2 in Git | Commit or stash — decide now |
+| 3 in any dimension | **WARNING** — surface to user, ask if they want to address now |
+| 4-5 in all dimensions | "System is healthy. Ready to build." |
+
+---
+
 ## Output Format
 
 ```
 G2W Health Check — [date]
 
-Docs:
-✅ ARCHITECTURE.md — in sync
-✅ FEATURES.md — in sync
-⚠️  ERRORS.md — ERR-01 marked critical, no activity in 3 sessions
-❌ CONVENTIONS.md — missing (not created yet)
+Docs:       ████████████████░░░░ 4/5
+Plan:       ████████████████████ 5/5
+Errors:     ████████████░░░░░░░░ 3/5
+Freshness:  ████████████████████ 5/5
+Git:        ████████████████░░░░ 4/5
 
-Plan:
-✅ Plan locked
-✅ Definition of done present
-⚠️  2 declared files may have been renamed since lock
-
-Errors:
-⚠️  ERR-01 — CRITICAL, unresolved
-✅ No stale "in progress" errors
+Overall: 4.2/5
+```
 
-CURRENT.md:
-✅ Looks fresh
+Then below the scores, show the detail for anything scoring 3 or below:
 
-Git:
-✅ No uncommitted verified changes
-✅ Last commit follows G2W format
+```
+⚠️  Errors: 3/5 — ERR-01 marked HIGH, unresolved, no activity in 3 sessions
+   → Action: Triage with user — fix or downgrade severity
 
-Overall: ⚠️  WARNINGS FOUND — review before building
+⚠️  Docs: ... (if applicable)
 ```
 
+If overall is 4.0+ with no dimension below 3: "System is healthy. Ready to build."
+
+---
+
 ## After the Report
 
-- If ❌ FAIL items exist → fix them before any other work proceeds
-- If ⚠️ WARNING items exist → surface them to the user, ask if they want to address now or log for later
-- If all ✅ → "System is healthy. Ready to build."
+- If any dimension scores **1** → hard stop, fix before any other work
+- If any dimension scores **2** → fix now, use the action map
+- If any dimension scores **3** → surface to user, ask if they want to address now or later
+- If all dimensions score **4-5** → "System is healthy. Ready to build."
 
 ## Rules
 
 - Don't just check if files exist — read enough to assess if they're accurate
 - A doc that exists but is 6 months stale is worse than no doc (false confidence)
-- If you can't check something (no access, build required), say so — don't guess ✅
+- If you can't check something (no access, build required), say so — don't guess a 5
+- Score honestly. A 4 that should be a 2 is worse than the bug it hides.

package/skills/true2plan.md

@@ -5,6 +5,14 @@ description: Verify that what was built matches what the plan declared — PASS/
 
 # /g2w:true2plan
 
+## Prerequisites
+
+- `PLAN.md` exists and is locked in `~/.g2w/projects/[active-project]/` (cannot verify against a plan that doesn't exist)
+
+**Check this first. If no locked plan exists, tell the user there's nothing to verify against. Do not proceed.**
+
+---
+
 You are the verifier. Your job is not to say "looks good" — it is to confirm that every specific thing the plan declared was actually done, correctly.
 
 ## Steps
@@ -26,10 +34,13 @@ You are the verifier. Your job is not to say "looks good" — it is to confirm t
 
    Run each verification step from the plan. Record actual result vs expected.
 
-5. **Regression check:**
+5. **Regression check (Golden Cases):**
 
-   - What was working before this change (pull from TESTING.md)?
-   - Is that list still intact? → PASS / FAIL
+   - Read the Golden Cases section of `TESTING.md`
+   - Run every golden case — not just the ones that seem related to this change
+   - Any golden case failure = automatic FAIL, even if all plan items pass
+   - Update "Last Verified" column for each case that passes
+   - Also check: what was working before this change? Is that list still intact? → PASS / FAIL
 
 6. **Output the report:**
    ```