chore: split CLAUDE.md into subdirectory files for cli/ and web/#932
Conversation
Root CLAUDE.md was 40.5k chars, triggering the "large CLAUDE.md" performance warning. Extracted CLI reference (flags, hints, env vars, exit codes, config, per-command flags) to cli/CLAUDE.md and web dashboard content (commands, package structure, design system component inventory, token rules, TS6/Storybook 10 post-training reference) to web/CLAUDE.md. Root keeps one-liner pointers. Result: 40.5k -> 22.7k chars (44% reduction). Claude Code auto-loads subdirectory CLAUDE.md files when working in those directories, so no information is lost. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
📜 Recent review details⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)
🧰 Additional context used🧠 Learnings (37)📓 Common learnings📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-15T18:17:43.675ZApplied to files:
📚 Learning: 2026-03-15T21:32:02.880ZApplied to files:
📚 Learning: 2026-03-15T21:32:02.880ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-15T21:32:02.880ZApplied to files:
📚 Learning: 2026-03-21T14:12:17.848ZApplied to files:
📚 Learning: 2026-03-21T12:54:22.557ZApplied to files:
📚 Learning: 2026-03-21T14:12:17.848ZApplied to files:
📚 Learning: 2026-03-16T19:52:03.656ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.468ZApplied to files:
📚 Learning: 2026-03-15T20:45:14.430ZApplied to files:
📚 Learning: 2026-03-21T12:54:22.557ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-19T07:12:14.508ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-15T21:20:09.993ZApplied to files:
📚 Learning: 2026-03-15T18:17:43.675ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-14T15:43:05.601ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-30T14:15:14.467ZApplied to files:
📚 Learning: 2026-03-14T15:43:05.601ZApplied to files:
🔇 Additional comments (4)
WalkthroughThe pull request consolidates documentation by moving detailed CLI and Web Dashboard information from the main Suggested labels
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
There was a problem hiding this comment.
Code Review
This pull request refactors the project's documentation by moving detailed instructions and reference material for the CLI and Web Dashboard from the root CLAUDE.md into dedicated CLAUDE.md files within their respective directories. This change improves the organization of the documentation and reduces the size of the main entry point. I have no feedback to provide.
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Snapshot WarningsEnsure that dependencies are being submitted on PR branches. Re-running this action after a short time may resolve the issue. See the documentation for more information and troubleshooting advice. Scanned FilesNone |
🤖 I have created a release *beep* *boop* --- ## [0.5.2](v0.5.1...v0.5.2) (2026-03-31) ### Features * harden activity feed API ([#838](#838), [#839](#839), [#840](#840)) ([#937](#937)) ([c0234ad](c0234ad)) * provider usage metrics, model capabilities, and active health probing ([#935](#935)) ([1434c9c](1434c9c)) * runtime sink configuration via SettingsService ([#934](#934)) ([16c3f23](16c3f23)) * Settings page comprehensive redesign ([#936](#936)) ([#939](#939)) ([6d9ac8b](6d9ac8b)) ### Maintenance * bump astro from 6.1.1 to 6.1.2 in /site in the all group ([#940](#940)) ([ffa24f0](ffa24f0)) * bump pygments from 2.19.2 to 2.20.0 ([#931](#931)) ([9993088](9993088)) * bump the all group with 2 updates ([#942](#942)) ([aea37f8](aea37f8)) * bump typescript-eslint from 8.57.2 to 8.58.0 in /web in the all group ([#941](#941)) ([24f024c](24f024c)) * split CLAUDE.md into subdirectory files for cli/ and web/ ([#932](#932)) ([f5cfe07](f5cfe07)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
## Summary Corrects the "NATS Client Library" section of `docs/architecture/decisions.md`. The 2026-04-11 ADR (PR #1228, closing #1217) concluded that `nats-core` "lacks JetStream, KV store, and durable consumers" and used that to justify staying on `nats-py==2.14.0`. caspervonb pointed out on that PR that the conclusion is based on a misread of the modular client family: `nats-core` is the protocol layer, and JetStream/KV live in companion packages (`nats-jetstream` and `nats-key-value`), mirroring the `nats.js` v3 split. The rewritten section records: - A short Correction note citing caspervonb's comment and #2037 (sanctioned framing). - The live package state (verified 2026-05-24 against the PyPI JSON API and `nats-io/nats.py` main): `nats-core 0.2.0`, `nats-jetstream 0.3.0` (both Beta on PyPI), `nats-key-value 0.1.0` (Beta, workspace-only, not yet on PyPI), and `nats-py 2.14.0` still the current monolith. - That upstream `nats-io/nats.py` PR [#932](nats-io/nats.py#932) (the `inspect.iscoroutinefunction` fix for Python 3.14) merged 2026-05-13 but has not been tagged for release yet. - A four-row candidate table replacing the prior wrong rejection of `nats-core`. - A JetStream API-surface delta and a KV API-surface delta, both grounded in the actual call sites under `src/synthorg/communication/bus/` and the upstream source files. Includes a confirmed regression risk for `publish_batch`: `nats-jetstream 0.3.0` does not expose `publish_async` / `publish_async_completed` on either `JetStream` or `Stream`. - A trigger-based revisit replacing the prior fixed 2026-06-10 checkpoint: (A) unpin to `nats-py>=2.15` when that release ships, (B) re-evaluate migration when `nats-key-value` is on PyPI AND the family is at 1.0, (C) re-evaluate urgency if `nats-py` is silent for six months. Plus a 2026-08-01 calendar revisit so a quiet period does not let the trigger drift. **Decision: stay on `nats-py==2.14.0`** with the scoped `filterwarnings` entry, per user-confirmed Path A on 2026-05-24. No follow-up migration issue filed; acceptance criterion 4 of #2037 is satisfied vacuously by the user's choice and durably captured by the Trigger-based revisit section. ## Scope Docs-only. No changes to `src/synthorg/communication/bus/**`, `pyproject.toml`, or the scoped `filterwarnings` entry. ## Test plan - `git diff main...HEAD` confirms only `docs/architecture/decisions.md` is touched. - Local pre-commit (`markdownlint`, `trim trailing whitespace`, `fix end of files`, `no em-dashes`, `codespell`) clean on commit. - Local pre-push (`lychee`, `doc numeric macros`, etc.) clean on push. - ADR claims spot-checked against the codebase by `docs-consistency` agent: every file path, API call, error type, and pin location confirmed accurate (see review coverage below). ## Review coverage Pre-reviewed by 3 agents on the corrected ADR: - `docs-consistency`: zero findings; every concrete claim in the ADR verified against the codebase. - `comment-quality-rot`: one Minor finding (migration framing carried over from the prior ADR text in the Context paragraph); fixed in `1b1ee7b1e`. - `issue-resolution-verifier`: all four acceptance criteria of #2037 marked RESOLVED. Closes #2037
Summary
cli/CLAUDE.mdweb/CLAUDE.mdTest plan
cli/CLAUDE.mdloads when working on CLI codeweb/CLAUDE.mdloads when working on web dashboard codeReview coverage
Quick mode (docs-only changes, no agents needed).
🤖 Generated with Claude Code