sequant 2.7.0 → 2.9.0

package/dist/marketplace/external_plugins/sequant/skills/qa/scripts/quality-checks.sh

@@ -127,6 +127,9 @@ echo ""
 # Track cache hits/misses for final report
 declare -A CACHE_STATUS
 
+# Track blocking issues
+TAUTOLOGY_BLOCKING=false
+
 # =============================================================================
 # 1. Type safety check - detect 'any' type usage
 # =============================================================================
@@ -355,7 +358,76 @@ else
 fi
 
 # =============================================================================
-# 10. Shell Script Semantic Checks (unused functions, integration)
+# 10. Test Tautology Detection (AC-1 through AC-5)
+# =============================================================================
+echo ""
+echo "🔬 Running test tautology detection..."
+
+# Check for test files in the diff
+test_files_in_diff=$(git diff main...HEAD --name-only | grep -E '\.(test|spec)\.[jt]sx?$' || true)
+
+if [[ -z "$test_files_in_diff" ]]; then
+  CACHE_STATUS["test-quality"]="SKIP"
+  echo "   ⏭️  No test files in diff, skipping tautology check"
+else
+  if cache_check "test-quality"; then
+    CACHE_STATUS["test-quality"]="HIT"
+    cached_result=$(cache_get "test-quality")
+    tautology_passed=$(echo "$cached_result" | grep -o '"passed":\s*[^,}]*' | cut -d: -f2 | tr -d ' ')
+    tautology_message=$(echo "$cached_result" | grep -o '"message":\s*"[^"]*"' | cut -d'"' -f4)
+
+    if [[ "$tautology_passed" == "true" ]]; then
+      echo "   ✅ Test tautology: $tautology_message (cached)"
+    else
+      echo "   ⚠️  Test tautology: $tautology_message (cached)"
+    fi
+  else
+    CACHE_STATUS["test-quality"]="MISS"
+
+    # Check if tautology detector script exists
+    TAUTOLOGY_CLI=""
+    if [[ -f "$SCRIPT_DIR/../../../scripts/qa/tautology-detector-cli.ts" ]]; then
+      TAUTOLOGY_CLI="$SCRIPT_DIR/../../../scripts/qa/tautology-detector-cli.ts"
+    elif [[ -f "scripts/qa/tautology-detector-cli.ts" ]]; then
+      TAUTOLOGY_CLI="scripts/qa/tautology-detector-cli.ts"
+    fi
+
+    if [[ -n "$TAUTOLOGY_CLI" ]] && command -v npx &> /dev/null; then
+      tautology_output=$(npx tsx "$TAUTOLOGY_CLI" --json 2>&1) || tautology_exit=$?
+
+      if [[ -z "$tautology_exit" ]]; then
+        tautology_exit=0
+      fi
+
+      # Parse JSON output
+      tautology_status=$(echo "$tautology_output" | grep -o '"status":"[^"]*"' | cut -d'"' -f4 || echo "none")
+      total_tests=$(echo "$tautology_output" | grep -o '"totalTests":[0-9]*' | cut -d: -f2 || echo "0")
+      total_tautological=$(echo "$tautology_output" | grep -o '"totalTautological":[0-9]*' | cut -d: -f2 || echo "0")
+
+      if [[ "$tautology_status" == "skip" ]]; then
+        echo "   ⏭️  No test blocks found in changed files"
+        cache_set "test-quality" true "No test blocks found" "{\"totalTests\":0,\"tautological\":0}"
+      elif [[ "$tautology_status" == "blocking" ]]; then
+        echo "   ❌ BLOCKER: $total_tautological/$total_tests test blocks are tautological (>50%)"
+        echo "      Tautological tests don't call production code and provide zero regression protection."
+        cache_set "test-quality" false "$total_tautological/$total_tests tests tautological (>50%)" "{\"totalTests\":$total_tests,\"tautological\":$total_tautological}"
+        TAUTOLOGY_BLOCKING=true
+      elif [[ "$tautology_status" == "warning" ]]; then
+        echo "   ⚠️  WARNING: $total_tautological/$total_tests test blocks are tautological"
+        cache_set "test-quality" true "$total_tautological/$total_tests tests tautological" "{\"totalTests\":$total_tests,\"tautological\":$total_tautological}"
+      else
+        echo "   ✅ Test tautology: All tests call production code"
+        cache_set "test-quality" true "All tests call production code" "{\"totalTests\":$total_tests,\"tautological\":0}"
+      fi
+    else
+      echo "   ⚠️  Test tautology detector not available, skipping..."
+      CACHE_STATUS["test-quality"]="SKIP"
+    fi
+  fi
+fi
+
+# =============================================================================
+# 11. Shell Script Semantic Checks (unused functions, integration)
 # =============================================================================
 echo ""
 echo "🔍 Checking shell script semantics..."
@@ -385,8 +457,7 @@ else
 fi
 
 # =============================================================================
-# =============================================================================
-# 11.5. Skill Sync Check (when skill files modified)
+# 12. Skill Sync Check (when skill files modified)
 # =============================================================================
 echo ""
 skill_files_changed=$(git diff main...HEAD --name-only | grep -E '^\.(claude/skills|skills|templates/skills)/' || true)
@@ -431,7 +502,7 @@ else
 fi
 
 # =============================================================================
-# 12. Build Verification (cacheable - expensive operation)
+# 13. Build Verification (cacheable - expensive operation)
 # =============================================================================
 
 verify_build_against_main() {
@@ -613,7 +684,7 @@ echo "=========================================="
 echo ""
 echo "| Check | Cache Status |"
 echo "|-------|--------------|"
-for check in "type-safety" "deleted-tests" "scope" "size" "security" "semgrep" "build"; do
+for check in "type-safety" "deleted-tests" "scope" "size" "security" "semgrep" "test-quality" "build"; do
   status="${CACHE_STATUS[$check]:-MISS}"
   if [[ "$status" == "HIT" ]]; then
     echo "| $check | ✅ HIT |"
@@ -629,7 +700,7 @@ echo ""
 hit_count=0
 miss_count=0
 skip_count=0
-for check in "type-safety" "deleted-tests" "scope" "size" "security" "semgrep" "build"; do
+for check in "type-safety" "deleted-tests" "scope" "size" "security" "semgrep" "test-quality" "build"; do
   status="${CACHE_STATUS[$check]:-MISS}"
   if [[ "$status" == "HIT" ]]; then
     ((hit_count++))
@@ -646,15 +717,17 @@ if [[ $hit_count -gt 0 ]]; then
 fi
 echo ""
 
-# Write structured cache metrics JSON for sequant observability (AC-7)
-# This file is read by run.ts to populate PhaseLog.cacheMetrics
+# Write structured cache metrics JSON for sequant observability (#278/AC-7)
+# This file is read by worktree-manager.ts to populate PhaseLog.cacheMetrics
+# (surfaced via `sequant logs`). Written before the blocking exit logic below so
+# metrics are always emitted, even when a check blocks.
 CACHE_METRICS_DIR=".sequant/.cache/qa"
 mkdir -p "$CACHE_METRICS_DIR"
 
 # Build JSON with per-check status
 CACHE_JSON="{\"hits\":$hit_count,\"misses\":$miss_count,\"skipped\":$skip_count,\"checks\":{"
 first=true
-for check in "type-safety" "deleted-tests" "scope" "size" "security" "semgrep" "build"; do
+for check in "type-safety" "deleted-tests" "scope" "size" "security" "semgrep" "test-quality" "build"; do
   $first || CACHE_JSON+=","
   CACHE_JSON+="\"$check\":\"${CACHE_STATUS[$check]:-MISS}\""
   first=false
@@ -664,5 +737,16 @@ echo "$CACHE_JSON" > "$CACHE_METRICS_DIR/cache-metrics.json"
 
 echo "✅ Quality checks complete"
 
-# Exit with build verification result if it indicates a problem
-exit $build_verification_result
+# Exit with appropriate code based on blocking issues
+# Priority: build verification > tautology blocking
+if [[ $build_verification_result -ne 0 ]]; then
+  exit $build_verification_result
+fi
+
+if [[ "$TAUTOLOGY_BLOCKING" == "true" ]]; then
+  echo ""
+  echo "❌ BLOCKED: >50% of test blocks are tautological (AC-4 violation)"
+  exit 1
+fi
+
+exit 0

package/dist/marketplace/external_plugins/sequant/skills/references/shared/framework-gotchas.md

@@ -0,0 +1,186 @@
+# Framework Gotchas
+
+Common framework-specific issues encountered in this project. Check this reference when encountering unexpected runtime errors or build failures.
+
+## AG Grid (v35+)
+
+### Module Registration Required
+
+AG Grid v35 changed to explicit module registration. If you see errors like "Module not registered" or grid features not working:
+
+```typescript
+import { ModuleRegistry } from 'ag-grid-community';
+import { ClientSideRowModelModule } from 'ag-grid-community';
+
+// Register before using AG Grid components
+ModuleRegistry.registerModules([ClientSideRowModelModule]);
+```
+
+**Common modules to register:**
+- `ClientSideRowModelModule` - Basic row model
+- `CsvExportModule` - CSV export functionality
+- `InfiniteRowModelModule` - Infinite scrolling
+
+**Docs:** [AG Grid v35 Migration Guide](https://www.ag-grid.com/javascript-data-grid/modules/)
+
+### CSS Import Changes
+
+Styles are now in a separate package. Update imports:
+
+```typescript
+// Before v35
+import 'ag-grid-community/styles/ag-grid.css';
+import 'ag-grid-community/styles/ag-theme-alpine.css';
+
+// v35+
+import 'ag-grid-community/styles/ag-grid.css';
+import 'ag-grid-community/styles/ag-theme-quartz.css';  // New default theme
+```
+
+---
+
+## React 19
+
+### use() Hook
+
+React 19 introduces the `use()` hook for reading resources (Promises, Context) during render:
+
+```typescript
+// Reading context with use()
+function Component() {
+  const theme = use(ThemeContext);  // Can be called conditionally
+  return <div className={theme} />;
+}
+
+// Reading promises with use()
+function UserProfile({ userPromise }) {
+  const user = use(userPromise);  // Suspends until resolved
+  return <div>{user.name}</div>;
+}
+```
+
+**Gotcha:** `use()` can be called inside loops and conditionals (unlike other hooks).
+
+**Docs:** [React 19 Release Notes](https://react.dev/blog/2024/12/05/react-19)
+
+### Concurrent Features On by Default
+
+Concurrent rendering is now the default. Watch for:
+- State updates during render (can cause infinite loops)
+- External store subscriptions (use `useSyncExternalStore`)
+- Mutable refs during render
+
+---
+
+## Next.js 15
+
+### Changed Caching Defaults
+
+Next.js 15 no longer caches `fetch()` requests by default:
+
+```typescript
+// Before Next.js 15 - cached by default
+const data = await fetch('/api/data');
+
+// Next.js 15 - NOT cached by default
+const data = await fetch('/api/data');  // Always fresh
+
+// To cache, explicitly opt-in:
+const data = await fetch('/api/data', { cache: 'force-cache' });
+
+// Or use next.revalidate:
+const data = await fetch('/api/data', { next: { revalidate: 3600 } });
+```
+
+**Docs:** [Next.js 15 Caching](https://nextjs.org/docs/app/building-your-application/caching)
+
+### Async Request APIs
+
+Dynamic APIs are now async. Update your code:
+
+```typescript
+// Before Next.js 15
+export default function Page({ params }) {
+  const { id } = params;
+  // ...
+}
+
+// Next.js 15+
+export default async function Page({ params }) {
+  const { id } = await params;
+  // ...
+}
+
+// Same for cookies, headers, searchParams
+import { cookies, headers } from 'next/headers';
+
+// Before
+const cookieStore = cookies();
+
+// After
+const cookieStore = await cookies();
+```
+
+---
+
+## Tailwind v4
+
+### CSS-First Configuration
+
+Tailwind v4 uses CSS for configuration instead of `tailwind.config.js`:
+
+```css
+/* tailwind.css */
+@import "tailwindcss";
+
+@theme {
+  --color-primary: #3b82f6;
+  --font-sans: "Inter", sans-serif;
+}
+```
+
+**Gotcha:** The `@config` directive is removed. Use `@theme` in CSS.
+
+**Docs:** [Tailwind v4 Migration](https://tailwindcss.com/docs/v4-beta)
+
+### Class Syntax Changes
+
+Some utility classes have been renamed or changed:
+
+```html
+<!-- v3 -->
+<div class="bg-opacity-50">
+
+<!-- v4 - use color modifiers -->
+<div class="bg-blue-500/50">
+```
+
+---
+
+## Adding New Gotchas
+
+When you encounter a framework-specific issue that cost debugging time, add it here following this template:
+
+```markdown
+## [Framework Name] (v[X]+)
+
+### [Issue Title]
+
+[Brief description of the problem and when it occurs]
+
+\`\`\`typescript
+// Code example showing the fix or correct approach
+\`\`\`
+
+**Gotcha:** [Key insight or common mistake]
+
+**Docs:** [Link to official documentation or changelog]
+```
+
+### Guidelines for Adding Entries
+
+1. **Version-specific:** Always include the version where the behavior changed
+2. **Code examples:** Show both "before" and "after" when applicable
+3. **Link to docs:** Include official documentation or migration guide links
+4. **Keep it brief:** Focus on the fix, not the full explanation
+5. **Update existing entries:** Prefer updating existing sections over creating duplicates

package/dist/marketplace/external_plugins/sequant/skills/reflect/SKILL.md

@@ -120,21 +120,35 @@ For each proposal, specify:
 
 ### **Documentation Health Check**
 
-Review CLAUDE.md size and relevance:
-- Current line count (target: 700-800)
-- Sections that feel bloated
-- Sections that are missing
-- Redundancy check
-- Extract candidates (sections >50 lines)
-- Recommendation: [Prune | Expand | Restructure | Extract | Good as-is]
+**CLAUDE.md is an index, not a knowledge store.** Durable knowledge belongs in
+auto-memory, `docs/`, or the relevant skill; CLAUDE.md holds only what must be
+loaded into *every* session (commit rules, hook gotchas, skill-invocation
+rules). A short CLAUDE.md is a sign the other tiers are doing their job — do
+**not** recommend padding it toward some line count. There is no target length.
+
+Review CLAUDE.md relevance:
+- Does every line still apply, and is it still accurate?
+- Anything that only matters in one workflow → move to that skill or `docs/`
+- Anything that is durable session-to-session context → auto-memory
+- Redundancy check (same rule stated here and in a skill)
+- Extract candidates (sections >50 lines — CLAUDE.md should rarely have any)
+- Recommendation: [Prune | Restructure | Extract | Good as-is]
+
+Also check the **memory** tier, which carries most of this repo's knowledge:
+- Entries citing script flags, CLI behavior, or `file:line` **rot silently** —
+  spot-check any entry you relied on this session against current code and fix
+  it. A wrong memory is worse than a missing one.
+- Index (`MEMORY.md`) one-liners still accurate?
 
 ### **Action Items**
 
-Generate a checklist:
-- [ ] Add section to CLAUDE.md: [topic]
-- [ ] Update slash command: [command name]
-- [ ] Move to docs/archive/: [file name]
-- [ ] Create new command: [command name]
+Generate a checklist. Prefer concrete targets — a file, a memory entry, a
+command — over intentions:
+- [ ] Correct/remove a stale memory entry: [name] (verify against current code first)
+- [ ] Add a memory entry for: [durable lesson]
+- [ ] Update skill: [name] — remember all three skill dirs
+- [ ] Update docs: [path] (check main README + marketplace README + docs/)
+- [ ] Add a pointer to CLAUDE.md: [one line + link] — only if needed most sessions
 - [ ] Remove outdated content: [location]
 
 ## Workflow Analytics
@@ -172,7 +186,7 @@ At the end of reflection, ask:
 - [ ] **Session Summary** - What was accomplished, what went well, friction points
 - [ ] **Effectiveness Analysis** - Token efficiency, context gathering, pattern reuse
 - [ ] **Proposed Changes** - Specific changes with target files and rationale
-- [ ] **Documentation Health** - Line count, bloat assessment, recommendations
+- [ ] **Documentation Health** - CLAUDE.md relevance/accuracy (not length) + memory-tier rot check
 - [ ] **Action Items** - Checklist of concrete next steps
 
 **DO NOT respond until all items are verified.**

package/dist/marketplace/external_plugins/sequant/skills/reflect/references/documentation-tiers.md

@@ -1,70 +1,82 @@
 # Documentation Tiers
 
-Organize information by access frequency:
-
-## Tier 1: Hot Path (CLAUDE.md)
-
-- Used in 50%+ of sessions
-- Core architecture decisions
-- Most common commands and patterns
-- **Target: 700-800 lines** (check with `wc -l CLAUDE.md`)
-- Quick summaries with links to detailed docs
-- Review monthly
-
-**Keep in CLAUDE.md:**
-- ✅ Core architecture patterns (database, routing, components)
-- ✅ Most common commands (development, discovery, enrichment)
-- ✅ Critical patterns (validation, audit logging, state management)
-- ✅ Quick reference information needed in 50%+ of sessions
-
-## Tier 2: Reference (docs/ folder)
-
-- Used in 10-50% of sessions
-- Detailed specs, schemas, guides
-- Can be 1000+ lines per doc
-- Review quarterly
-
-**Current specialized docs:**
-- `ARCHITECTURE.md` - System architecture overview
-- `DATA_PIPELINE.md` - Data processing workflows
-- `TESTING.md` - Testing patterns and strategies
-- `ADMIN_CMS_ARCHITECTURE.md` - Full CMS architecture
-
-## Tier 3: Archive (docs/archive/)
-
-- Used in <10% of sessions
-- Historical context, deprecated patterns
-- Move here after 6 months of non-use
-- Keep for searchability, not active use
-
-## Tier 4: Code Comments
-
-- Implementation-specific details
-- Edge case handling
-- Why certain approaches were chosen
-- Lives with the code, not in docs
-
-## When to Extract to Separate Docs
-
-Move from CLAUDE.md to docs/ when:
-- ✅ Section exceeds 50 lines
-- ✅ Contains detailed workflow steps (>3 steps)
-- ✅ Has extensive examples or command variations
-- ✅ Used occasionally but not in every session
-- ✅ Could evolve independently
-
-## Documentation Health Metrics
-
-**CLAUDE.md Health Check:**
-- Current line count vs target (700-800)
-- Lines added in last month
-- Sections that feel bloated
-- Sections that are missing
-- Redundancy between CLAUDE.md and docs/
-
-**Recommendations:**
-- **Prune:** >900 lines, multiple bloated sections
-- **Expand:** <600 lines, missing critical patterns
-- **Restructure:** Hard to find information
-- **Extract:** Multiple sections >50 lines
-- **Good as-is:** 700-800 lines, balanced content
+Where knowledge lives in this repo, by how often it's needed and how long it stays true.
+
+**There are no line-count targets.** Judge a tier by whether the right reader
+finds the right thing, not by size. A short CLAUDE.md means the other tiers are
+working, not that it needs filling.
+
+## Tier 1: CLAUDE.md — the always-loaded index
+
+Loaded into **every** session, so everything here is a tax on every session.
+
+**Keep only:**
+- ✅ Rules with no natural home in a skill or doc (commit conventions, hook gotchas)
+- ✅ Pointers — a one-line "here's the trap, here's the link"
+- ✅ Things that are wrong to learn late (e.g. skill-invocation namespacing)
+
+**Move out:**
+- ❌ Anything that matters in one workflow → that skill
+- ❌ Anything explanatory or >~10 lines → `docs/` and link to it
+- ❌ Session-to-session context about *this developer's* work → auto-memory
+
+## Tier 2: Auto-memory — the main knowledge store
+
+`~/.claude/projects/<project>/memory/`, indexed by `MEMORY.md`. This is where
+most of this repo's hard-won knowledge actually lives (100+ entries): pitfalls,
+feedback, architecture decisions, roadmap state.
+
+- One fact per file; `MEMORY.md` carries a one-line pointer.
+- Best tier for "I learned this the hard way and would re-learn it otherwise".
+
+**Its failure mode is rot, not bloat.** Entries citing script flags, CLI
+behavior, or `file:line` go stale silently, and a *wrong* memory is worse than a
+missing one — it gets trusted. Verify before asserting; fix on sight.
+
+## Tier 3: docs/ — reference for humans
+
+Real structure: `concepts/`, `features/`, `guides/`, `reference/`,
+`getting-started/`, `examples/`, `internal/`, `incidents/`, `investigations/`.
+
+- Detailed specs, architecture, runbooks. Length is fine here.
+- User-facing behavior changes must land here, and often in **more than one
+  place** — check the main README, the marketplace README, and `docs/`.
+- Review when the behavior it describes changes, not on a calendar.
+
+## Tier 4: Skills — workflow instructions
+
+`skills/`, `templates/skills/`, `.claude/skills/` — **three real copies**;
+fix all three or `sequant init`/`update` regenerates the bug (CI enforces this
+via `npm run lint:skill-sync`).
+
+- Procedure a skill must follow belongs in its `SKILL.md`.
+- Detail a skill needs only sometimes → its `references/`, linked from `SKILL.md`.
+- **When editing a SKILL.md, grep its `references/` for the same claim.** Prose
+  specs of a rule drift out of sync with the rule itself.
+
+## Tier 5: Code comments
+
+Constraints the code can't show — why this approach, what breaks otherwise.
+Not what the next line does, and not where it came from.
+
+## When to extract from CLAUDE.md
+
+- ✅ It's explanatory rather than a pointer
+- ✅ It only applies to one workflow or one command
+- ✅ It has examples, steps, or rationale
+- ✅ It could evolve independently of the rest
+
+## Health check
+
+**CLAUDE.md:** is every line still true, still needed in *most* sessions, and
+not duplicated in a skill? Recommend `Prune | Restructure | Extract | Good as-is`
+— never "Expand".
+
+**Memory:** spot-check entries relied on this session against current code.
+Are `MEMORY.md` one-liners still accurate? Any entry superseded by shipped work?
+
+**docs/:** does anything contradict what shipped? Behavior changes are the usual
+source of drift.
+
+**Skills:** are the three copies in sync, and does each `SKILL.md` agree with its
+own `references/`?

package/dist/marketplace/external_plugins/sequant/skills/reflect/references/phase-reflection.md

@@ -70,26 +70,42 @@ Focus on QA/review effectiveness after `/qa`:
 
 ## Good Reflection Examples
 
-### Documentation Improvement
+Note what these have in common: each names a **specific file and a specific
+wrong line**, and each was *verified* before being proposed. A reflection that
+proposes fixing something you have not opened is a guess.
 
-> **Friction Point:** Spent 10 minutes searching for how neighborhood extraction works across multiple files.
+### Correcting a stale memory
+
+> **Friction Point:** Followed a memory that prescribed `echo y | cleanup-worktree.sh`; the script had since grown a real `--yes` flag and a merge gate (#750).
 >
-> **Root Cause:** Process is documented in docs/AUTO_NEIGHBORHOOD_ENRICHMENT.md (tier 2) but not referenced in CLAUDE.md's discovery pipeline section (tier 1).
+> **Root Cause:** Memory entries citing script flags rot silently when the script ships a change. The entry read as authoritative and was 67 days old.
 >
 > **Proposal:**
-> - **Type:** Add
-> - **Target:** CLAUDE.md, line 230 (Discovery Methods section)
-> - **Content:** Add one-line reference: "Neighborhoods auto-extracted via ZIP mapping (see docs/AUTO_NEIGHBORHOOD_ENRICHMENT.md)"
-> - **Priority:** Medium
-> - **Risk:** Low (just adding a signpost)
+> - **Type:** Update
+> - **Target:** `feedback_cleanup_worktree_after_gh_merge`
+> - **Content:** Replace the `echo y |` workaround with the shipped flags; add the `--delete-branch`-fails-when-a-worktree-holds-the-branch trap.
+> - **Priority:** High (a wrong memory is worse than a missing one — it gets trusted)
+> - **Risk:** Low (verified against the script's `--help` first)
+
+### Retiring guidance that a skill already implements
+
+> **Friction Point:** Was about to propose adding a diff-size threshold to `/qa` so small diffs skip sub-agents.
+>
+> **Root Cause:** The proposal was based on the skill text actually executed, which came from a **stale plugin cache** (1.20.3) rather than the repo (2.8.0). The repo's `/qa` already has the size gate. Invoking `sequant:qa` resolves to the installed plugin; bare `qa` resolves to `.claude/skills/`.
+>
+> **Proposal:**
+> - **Type:** Withdraw + document the routing trap
+> - **Target:** the proposal itself; memory entry for the skew
+> - **Priority:** High (the finding was an artifact, and acting on it would have duplicated shipped work)
+> - **Risk:** None — verification *removed* work rather than adding it
 
-### Documentation Pruning
+### Pruning content inherited from another project
 
-> **Bloat:** CLAUDE.md has 150 lines on Mapbox troubleshooting that solved a one-time issue 6 months ago.
+> **Bloat:** `references/documentation-tiers.md` prescribed a 700–800 line CLAUDE.md target and named `ARCHITECTURE.md`, `DATA_PIPELINE.md`, `ADMIN_CMS_ARCHITECTURE.md` as "current docs". None exist here; CLAUDE.md is 13 lines by design. Its "**Expand:** <600 lines" rule would have demanded ~590 lines of invented content.
 >
 > **Proposal:**
-> - **Type:** Remove + Archive
-> - **Target:** CLAUDE.md lines 450-600
-> - **Action:** Move to docs/archive/mapbox-troubleshooting-2024.md with note "Archived: Issue resolved in react-map-gl v7.1.0"
-> - **Priority:** High (saves 150 lines in hot path)
-> - **Risk:** Low (still searchable if issue recurs)
+> - **Type:** Restructure
+> - **Target:** `references/documentation-tiers.md` (×3 skill dirs)
+> - **Action:** Rewrite around this repo's real tiers (CLAUDE.md index → auto-memory → `docs/` → skills → code comments); drop all line targets.
+> - **Priority:** Medium
+> - **Risk:** Low (verified every named doc was absent before rewriting)