Skip to content

docs: contributor guide, architecture map, and per-provider docs#284

Merged
iamtoruk merged 1 commit intomainfrom
docs/contributor-guide
May 10, 2026
Merged

docs: contributor guide, architecture map, and per-provider docs#284
iamtoruk merged 1 commit intomainfrom
docs/contributor-guide

Conversation

@iamtoruk
Copy link
Copy Markdown
Member

Summary

  • Add CONTRIBUTING.md, docs/architecture.md, and 19 files under docs/providers/ (one per provider plus an index and the shared cline-parser helper).
  • Fix RELEASING.md: the CLI section claimed GitHub Actions auto-publishes on a v* tag. There is no such workflow; CLI publishing is manual via npm publish. Menubar automation (mac-v* tag firing release-menubar.yml) was accurate and is unchanged.
  • Anchor the CLAUDE.md line in .gitignore to /CLAUDE.md so it only ignores the root-level memory file, not docs/providers/claude.md on case-insensitive filesystems.

What is in docs/providers/

One file per integration. Each follows the same template: data path, storage format, caching, dedup key, quirks, and a "when fixing a bug here" checklist. Covers the 12 eager and 5 lazy providers registered in src/providers/index.ts plus the shared vscode-cline-parser helper.

Verification

All cited file paths, line numbers, function names, and counts were checked against current main:

  • 12 CLI commands (grep-confirmed against src/cli.ts).
  • 14 optimize detectors (grep-confirmed against src/optimize.ts).
  • 41 test files, 558 tests passing locally (npx vitest --run).
  • Five providers without test files today (claude, gemini, goose, qwen, antigravity), called out in CONTRIBUTING.md as a known gap.
  • A multi-agent style validator scanned for em dashes and AI filler; nothing flagged.
  • A multi-agent accuracy validator cross-checked every cited line number; corrections made (kiro, antigravity, vscode-cline-parser ranges) before committing.

Test plan

  • git diff main..docs/contributor-guide -- '.gitignore' shows only the single-character anchor change.
  • npm test still passes (no source files were touched).
  • Spot-check three or four docs/providers/*.md files against the corresponding src/providers/*.ts to confirm the cited line numbers still resolve to the right code.

Document the contributor onboarding path:
- CONTRIBUTING.md: setup, npm scripts, coding conventions, PR process,
  the block-claude-coauthor enforcement, and the five providers without
  test coverage today (claude, gemini, goose, qwen, antigravity).
- docs/architecture.md: 12-command CLI surface, parser pipeline, three
  cache layers, 14 optimize detectors, and the mac / gnome / build
  layouts with cited line numbers.
- docs/providers/: one file per provider (17 providers plus the shared
  vscode-cline-parser helper). Each covers data path, storage format,
  caching, dedup key, quirks, and a "when fixing a bug here" checklist.

Also fix two pre-existing documentation issues surfaced while writing
the new docs:
- RELEASING.md claimed GitHub Actions auto-publishes the CLI when a
  v* tag is pushed. There is no such workflow; CLI publishing is
  manual via npm publish. Updated the CLI section to reflect reality
  and kept the menubar (mac-v* tag) automation accurate.
- .gitignore had CLAUDE.md unanchored, which on case-insensitive
  filesystems also matched docs/providers/claude.md. Anchored to
  /CLAUDE.md so the root-level memory file stays ignored without
  affecting subdirectory docs.

All cited file paths, line numbers, function names, and test counts
were verified against current code (41 test files, 558 tests passing).
@iamtoruk iamtoruk merged commit 6746ecc into main May 10, 2026
3 checks passed
@iamtoruk iamtoruk deleted the docs/contributor-guide branch May 10, 2026 01:39
iamtoruk added a commit that referenced this pull request May 10, 2026
…285)

The provider table now points each row at its docs/providers/<name>.md
file (added in #284) instead of repeating a one-line path that the
per-provider doc covers in full. The Data Location column is dropped;
the new Doc column links to the markdown that owns the path, storage
format, dedup key, and known quirks.

The trailing sentence is updated to reference the per-provider docs as
the source of truth for data locations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant