3 commits

Author	SHA1	Message	Date
ivkond	015f073e9d	docs(#794): close implementation checklist and align RFC with @repo MCP surface ... - Mark Phases 1–7 in docs/superpowers/plans/2026-04-16-issue-794-implementation.md as complete, fold in the Issue #794 traceability map, and record the Final verification snapshot (tsc clean + 9 vitest files / 111 tests). - Update docs/superpowers/specs/2026-03-31-cross-index-impact-design.md to match the Issue #794 MCP model: * `group_impact` / `group_contracts` / `group_query` / `group_status` are NOT MCP tools. * `impact` / `query` / `context` accept `repo: "@<groupName>"` and optional `service` for monorepo boundary filtering. * Group state is exposed via `gitnexus://group/{name}/contracts` and `gitnexus://group/{name}/status` resources. * Add MCP migration table and refresh AI-context guidance. - Restate execution handoff: Phases 4 + 5 + 6 share one branch and must ship as a single squash-merge to avoid a half-migrated MCP surface. Closes #794 Made-with: Cursor	2026-04-19 13:37:47 +03:00
ivkond	2667c3cd72	docs(plan): tighten Issue #794 implementation plan after review ... Expand MCP dispatch model, contracts (GroupImpactResult, GroupContextResult), service semantics, timeout/safeLocalImpact, resolveGroupRepo placement, safeParseMeta behavior, Phase 3.3a/3.3b test split, parseUri rules, Phase 5 mapping, risks, and final verification commands. Made-with: Cursor	2026-04-16 00:49:36 +03:00
ivkond	be4458b650	docs: add design spec and implementation plan for PR #626 HIGH fixes ... Spec covers 4 HIGH-priority issues from review: path traversal via group name, gRPC proto regex nested braces, service boundary detector directory exclusions, double-close of LadybugDB pools. Plan: 6 tasks with TDD, ordered by complexity. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-02 12:55:18 +03:00