chore: scope published .claude bundle + housekeeping (#25)

* chore: scope published .claude bundle, fix changelog date, ignore local lock

- package.json files[]: replace the broad ".claude" entry with the
  supaschema bundle subpaths (.claude/hooks, .claude/rules,
  .claude/settings.json, .claude/skills/supaschema). The broad entry shipped
  6 unrelated .claude/skills/gitnexus/** SKILL.md files (local dev tooling)
  in the npm tarball; the consumer-facing agent bundle is unchanged.
- CHANGELOG.md: 0.1.1 was published 2026-06-14, not 2026-06-12.
- .gitignore: ignore .claude/scheduled_tasks.lock and .claude/plans
  (local runtime artifacts) so they never enter a commit or local pack.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: keep packaged agent docs consistent with the scoped bundle

The shipped AGENTS.md/CLAUDE.md carried an auto-injected GitNexus block
referencing .claude/skills/gitnexus/** — now excluded from the tarball —
so a consumer following the bundled guidance hit missing skill files.

- Strip the GitNexus 'Code Intelligence' block from AGENTS.md (it is local
  dev tooling for this repo, not consumer-facing operator guidance).
- Drop CLAUDE.md from files[]: it is just '@AGENTS.md' plus the same local
  GitNexus block — not consumer content. Consumers get AGENTS.md and the
  .claude/.codex/.agents supaschema bundle directly.

npm pack --dry-run now ships zero gitnexus/CLAUDE.md references.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Author: jmclaughlin724

.gitignore

@@ -10,3 +10,5 @@ benchmarks/results
 .envrc
 .mcp.json
 .gitnexus
+.claude/scheduled_tasks.lock
+.claude/plans

AGENTS.md

@@ -89,47 +89,3 @@ npm run docs:check      # Mintlify validation, links, accessibility
 - For package, release, or bundled agent-surface changes, run `npm run check:package` or `npm pack --dry-run` as appropriate.
 - For docs-only changes, run `npm run docs:check` when Mintlify pages or navigation are touched.
 - Before merge or release, `npm run check`, `npm run check:package`, `npm run fixture:verify`, `npm run corpus:check`, and the relevant benchmark/docs checks should be clean.
-
-<!-- gitnexus:start -->
-# GitNexus — Code Intelligence
-
-This project is indexed by GitNexus as **supaschema** (3480 symbols, 6337 relationships, 300 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.
-
-> If any GitNexus tool warns the index is stale, run `npx gitnexus analyze` in terminal first.
-
-## Always Do
-
-- **MUST run impact analysis before editing any symbol.** Before modifying a function, class, or method, run `gitnexus_impact({target: "symbolName", direction: "upstream"})` and report the blast radius (direct callers, affected processes, risk level) to the user.
-- **MUST run `gitnexus_detect_changes()` before committing** to verify your changes only affect expected symbols and execution flows.
-- **MUST warn the user** if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
-- When exploring unfamiliar code, use `gitnexus_query({query: "concept"})` to find execution flows instead of grepping. It returns process-grouped results ranked by relevance.
-- When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use `gitnexus_context({name: "symbolName"})`.
-
-## Never Do
-
-- NEVER edit a function, class, or method without first running `gitnexus_impact` on it.
-- NEVER ignore HIGH or CRITICAL risk warnings from impact analysis.
-- NEVER rename symbols with find-and-replace — use `gitnexus_rename` which understands the call graph.
-- NEVER commit changes without running `gitnexus_detect_changes()` to check affected scope.
-
-## Resources
-
-| Resource | Use for |
-|----------|---------|
-| `gitnexus://repo/supaschema/context` | Codebase overview, check index freshness |
-| `gitnexus://repo/supaschema/clusters` | All functional areas |
-| `gitnexus://repo/supaschema/processes` | All execution flows |
-| `gitnexus://repo/supaschema/process/{name}` | Step-by-step execution trace |
-
-## CLI
-
-| Task | Read this skill file |
-|------|---------------------|
-| Understand architecture / "How does X work?" | `.claude/skills/gitnexus/gitnexus-exploring/SKILL.md` |
-| Blast radius / "What breaks if I change X?" | `.claude/skills/gitnexus/gitnexus-impact-analysis/SKILL.md` |
-| Trace bugs / "Why is X failing?" | `.claude/skills/gitnexus/gitnexus-debugging/SKILL.md` |
-| Rename / extract / split / refactor | `.claude/skills/gitnexus/gitnexus-refactoring/SKILL.md` |
-| Tools, resources, schema reference | `.claude/skills/gitnexus/gitnexus-guide/SKILL.md` |
-| Index, status, clean, wiki CLI commands | `.claude/skills/gitnexus/gitnexus-cli/SKILL.md` |
-
-<!-- gitnexus:end -->

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## 0.1.1 (2026-06-12)
+## 0.1.1 (2026-06-14)
 
 - Documentation site at supaschema.com: the Mintlify site moves to monorepo mode with the content root at `docs/`, an expanded information architecture (per-command reference pages, concept deep-dives, environments/database-URL resolution, Supabase integration guide, library API reference), and redirects from every legacy `/docs/*` URL.
 - Agent auto-run diff hooks: a PostToolUse hook for Claude Code and Codex senses a write to a schema-tree `.sql` file, runs `supaschema diff` then `supaschema check` to completion, and returns the generated migration name — or the blocking `SUPA_*` diagnostic — back to the agent as context. Wired in `.claude/settings.json` and `.codex/hooks.json`; the rules, skills, and `AGENTS.md` bundle describes the behavior.

package.json

@@ -24,10 +24,12 @@
   },
   "files": [
     ".agents",
-    ".claude",
+    ".claude/hooks",
+    ".claude/rules",
+    ".claude/settings.json",
+    ".claude/skills/supaschema",
     ".codex",
     "AGENTS.md",
-    "CLAUDE.md",
     "benchmarks/README.md",
     "benchmarks/compare.js",
     "benchmarks/fixtures",