docs(claude-md): structurally reorganize project guidance#18
Conversation
Manually merged: operator's authoritative edits (npm/pnpm framing from 1c212a1, parent-scope drop from 2ab34ca, portfolio-context dedup from 7cf00a2) as base, with structural improvements layered on top. - 8-section flat structure (Overview, Tech Stack by layer, Local Dev, Test Commands per layer with CI status, Build, Architecture, Project Structure, Conventions, Current Phase, Key Decisions, Do NOT) - Per-layer test command blocks with CI status annotations - Concrete paths: src-tauri/target/, dist/, ~/Library/Application Support/ com.jcc.app/jcc.db, ~/.jcc/gmail/ - Version pins: Tauri 2.x, tauri-specta 2.0.0-rc.21, Playwright 1.52+, anthropic>=0.52 - Expanded Do NOT list (13 items) Authored by 2x Sonnet 4.6 agents under Opus 4.7 coordination; the final file content is identical to the prior closed PR #17 / commit 8c45543 — this re-opens it on the correct base (polish/v1.0-improvements).
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6aa7cdcaf5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - **Framework:** React 19 + TypeScript (strict) + Vite | ||
| - **UI:** shadcn/ui + Tailwind CSS | ||
| - **State:** `useState` (component) → Zustand 5 (global UI) → TanStack Query 5 (SQLite/persistent data) | ||
| - **Package manager:** **pnpm** (pnpm v10 per CI; `pnpm-lock.yaml` is canonical — ignore `package-lock.json` which is an orphan from the initial template scaffold) |
There was a problem hiding this comment.
This switches the guidance to pnpm and tells agents to ignore package-lock.json, but the repo’s public setup docs still install/run with npm (README.md lines 36 and 43-46) and the release workflow caches npm and runs npm ci (.github/workflows/release.yml lines 40 and 57). When future dependency or script changes follow this file, they can update only pnpm-lock.yaml or run the wrong install path, leaving package-lock.json stale and breaking the release build that depends on it.
Useful? React with 👍 / 👎.
1 participant
Re-opens the work from closed PRs #15 and #17 on the correct base branch (
polish/v1.0-improvements). Content is identical to commit8c45543; only the lineage differs.Manually merged: operator's authoritative edits (npm/pnpm framing from
1c212a1, parent-scope drop from2ab34ca, portfolio-context dedup from7cf00a2) as base, with structural improvements from a prior Sonnet rewrite layered on top.Kept from polish (operator's authoritative edits):
Layered in from agent rewrite:
CI GREEN/CI STATUS: CHECK FIRST)src-tauri/target/,dist/,~/Library/Application Support/com.jcc.app/jcc.db,~/.jcc/gmail/anthropic>=0.52Flag: The
<!-- portfolio-context:start/end -->managed block was removed. When the personal-ops portfolio-context generator next syncs, it'll re-inject — and the "npm only" line will be wrong again. The Do NOT section's pnpm override now precedes the managed block as a hard rule, so agents won't be misled. Patching the generator is out of scope.Authored by 2x Sonnet 4.6 agents under Opus 4.7 coordination (Tier 2 pattern).