docs: sync CHANGELOG + mark older plans superseded after PR #91#92
Merged
Conversation
Bring documentation that wasn't touched by PR #91 itself into alignment with what actually shipped on 2026-05-24: - CHANGELOG.md: add the PR #91 entry under [Unreleased]. Covers all five change classes (Added: SQLite PRAGMA stanza + per-driver defaults + design spec; Changed: 7-tool MCP surface, LOG_FTS_ENABLED default; Removed: vectordb package + 14 MCP tools + graph_snapshots table + central-ops module dep; Fixed: 120-service OOM; Security: 28 OSV advisories on x/crypto, x/net, x/sys, Go stdlib, brace-expansion). - docs/IMPLEMENTATION_PLAN.md: add a status banner at the top noting the document is historical planning intent. Three specific sections are flagged as superseded — vector layer (5.3), MCP surface (5.4), hot/cold storage tiering (goal #4) — with pointers to the authoritative current sources (CLAUDE.md + 2026-05-24 design spec). No line-by-line rewrite; preserve the original record. - docs/superpowers/specs/2026-04-30-storage-rebalance-plan.md: add a superseded banner. The earlier plan was "drop FTS5, persist vectordb"; PR #91 did the opposite (kept FTS5, removed vectordb). The 24-hour search_logs cap from that plan did ship. Pure docs change. No code touched.
User policy clarification: agent-generated superpowers/* docs should not ship to git. Revising this PR accordingly: - Revert the banner I added to docs/superpowers/specs/2026-04-30-storage-rebalance-plan.md (file restored to origin/main state in this branch). - Drop the link to docs/superpowers/specs/2026-05-24-mcp-7tool-sqlite-survival-design.md from CHANGELOG and IMPLEMENTATION_PLAN. CLAUDE.md is the authoritative pointer. README.md additions to reflect the post-PR-#91 reality: - New "Production sizing" section between "Switching databases" and "OTLP Integration". Three-row table maps workload size to the recommended DB. Notes the auto-flipped SQLite defaults and the OTELCONTEXT_ALLOW_SQLITE_PROD=false guardrail. - Features list expanded to cover what shipped in PR #91 but wasn't yet surfaced to README readers: hybrid ingest backpressure, MCP per-call deadlines / concurrency semaphore / TTL cache / SSE keep-alives, log search (FTS5 default + pg_trgm + 24h cap on search_logs), per-tenant cardinality, auto-tuned SQLite PRAGMA stanza + per-driver defaults, self-instrumentation loopback guard.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pure documentation update — no code touched. Brings docs that weren't
part of #91
into alignment with what shipped on 2026-05-24.
Changes
CHANGELOG.md— adds the PR refactor: 7-tool MCP triage surface + SQLite survival tuning #91 entry under [Unreleased] acrossall five Keep-a-Changelog sections (Added / Changed / Removed / Fixed /
Security). Covers the SQLite tuning, the 7-tool MCP surface, the
vectordb / graph_snapshots / central-ops removals, the 120-service
OOM fix, and the 28 OSV advisories closed.
docs/IMPLEMENTATION_PLAN.md— adds a status banner at the topflagging three specific sections superseded by PR refactor: 7-tool MCP triage surface + SQLite survival tuning #91 (vector layer
in 5.3, MCP surface in 5.4, hot/cold storage tiering in goal chore(deps): update dependency framer-motion to v12.36.0 #4).
Preserves the 459 lines of original planning intent as historical
record; points readers to CLAUDE.md + the 2026-05-24 design spec for
current truth. No line-by-line rewrite.
docs/superpowers/specs/2026-04-30-storage-rebalance-plan.md—adds a superseded banner. That plan was "drop FTS5, persist vectordb";
PR refactor: 7-tool MCP triage surface + SQLite survival tuning #91 reversed both decisions (kept FTS5, removed vectordb). The
24-hour
search_logstime-window cap from that plan did ship andremains in effect.
Why now
Sanity check before the next release tag — these docs would have left
new readers confused about whether vectordb / the 21-tool surface still
exists. CLAUDE.md and the 2026-05-24 design spec are correct; the
older planning docs needed pointers added.
Test plan
defined at the bottom).
preserved bodies are unchanged.
PR refactor: 7-tool MCP triage surface + SQLite survival tuning #91's actual scope.