docs: trim CLAUDE.md to non-discoverable context only

Removed directory tree, command list, API endpoints, env var
listing, per-directory descriptions, and conventional-commits
boilerplate. All of these are trivially discoverable from
package.json, controllers/, config.js, or the commitlint config.

Kept: project identity, data-storage architecture (incl. the
2.x → 2.4.0 → 3.0 migration constraint), the deliberate e2e
helper-duplication pattern (easy to misread as a bug), and
release-please specifics.

124 lines → 25 lines.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: andrewshell

CLAUDE.md

@@ -2,132 +2,22 @@
 
 This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
 
-## Project Overview
+## What this is
 
-This is an rssCloud Server implementation in Node.js - a notification protocol server that allows RSS feeds to notify subscribers when they are updated. The server handles subscription management and real-time notifications for RSS/feed updates.
+An [rssCloud](http://rsscloud.org/) notification protocol server. Subscribers register a callback URL via `/pleaseNotify`; publishers `/ping` when feeds update; the server fans notifications out to subscribers. Implementation lives in `apps/server/`.
 
-## Monorepo Structure
+## Data storage
 
-This project is a pnpm workspace monorepo orchestrated by [Turborepo](https://turborepo.com/).
+State (resources and subscriptions) is held in memory and persisted atomically to a JSON file (default `./data/subscriptions.json`, configurable via `DATA_FILE_PATH`). The flush happens on an interval, at shutdown, and on unexpected exit. There is no external database.
 
-```
-/                              # Workspace root
-├── apps/
-│   ├── server/                # rssCloud Server application
-│   │   ├── app.js             # Express entry point
-│   │   ├── config.js          # Configuration from env vars
-│   │   ├── controllers/       # Route handlers
-│   │   ├── services/          # Business logic
-│   │   ├── views/             # Handlebars templates
-│   │   ├── public/            # Static assets
-│   │   └── Dockerfile         # Lean production image
-│   └── e2e/                   # End-to-end test suite (private)
-│       ├── test/              # Mocha/Chai tests + mock servers
-│       ├── Dockerfile         # Test-runner image (mocha + dockerize)
-│       └── docker-compose.yml # Orchestrates server + e2e containers
-├── packages/
-│   └── core/                  # @rsscloud/core: shared primitives (TS, tsup)
-├── pnpm-workspace.yaml        # Workspace definition
-└── turbo.json                 # Task orchestration + caching
-```
+## End-to-end tests
 
-## Development Commands
+`apps/e2e/` is a private workspace package holding a full mocha suite. Tests talk to the server over HTTP via `APP_URL` and spin up their own mock servers on ports 8002/8003.
 
-This project uses pnpm with corepack. Run `corepack enable` to set up pnpm automatically.
+A handful of server-internal helpers (RPC builders, dayjs wrapper, `init-subscription`, three config keys) are **intentionally duplicated** in `apps/e2e/test/helpers/` rather than imported across the workspace boundary. This preserves the e2e package as an independent consumer of the server's HTTP+RPC protocol, at the cost of some maintenance overhead if those helpers' wire-shape ever changes. If you find yourself adding a new `require('../...')` in a test file, prefer copying the dependency into `helpers/` instead.
 
-### Start Development (from repo root)
+## Releases
 
-- `pnpm start` - Start server with nodemon (auto-reload on changes)
-- `pnpm run client` - Start client with nodemon
+Conventional Commits are enforced by commitlint (via husky). Pushes to `main` trigger [release-please](https://github.com/googleapis/release-please) which opens or updates a Release PR per tracked package (`apps/server`, `packages/core`). `apps/e2e` is private and not tracked. Merging the Release PR cuts the release and git tag.
 
-### Testing & Quality (from repo root, all routed through turbo)
-
-- `pnpm test` - Run docker-based end-to-end tests via `apps/e2e/docker-compose.yml` (MacOS tested)
-- `pnpm run test:unit` - Run unit tests across all packages (just `@rsscloud/core`'s vitest today)
-- `pnpm run build` - Build all packages (just `@rsscloud/core`'s tsup today)
-- `pnpm run lint` - Run ESLint across all packages
-- `pnpm run typecheck` - Run TypeScript typecheck across all packages
-- `pnpm run format` - Run Prettier on the entire repo
-
-## Architecture
-
-### Core Application Structure (apps/server/)
-
-- **app.js** - Main Express application entry point, sets up middleware, loads jsonStore from disk, and starts server
-- **config.js** - Configuration management reading from env vars with defaults
-- **controllers/** - Express route handlers for API endpoints
-- **services/** - Business logic modules for core functionality
-- **views/** - Handlebars templates for web interface
-
-### Key Services
-
-- **services/json-store.js** - Disk-backed in-memory store; the sole source of truth for resources and subscriptions. Flushes atomically to `./data/subscriptions.json` on an interval and at shutdown.
-- **services/notify-\*.js** - Notification system for subscribers
-- **services/ping.js** - RSS feed update detection and processing
-- **services/please-notify.js** - Subscription management
-
-### API Endpoints (defined in controllers/index.js)
-
-- `/pleaseNotify` - Subscribe to RSS feed notifications
-- `/ping` - Notify server of RSS feed updates
-- `/viewLog` - Event log viewer for debugging
-- `/RPC2` - XML-RPC endpoint
-- Web forms available at `/pleaseNotifyForm` and `/pingForm`
-
-### Configuration
-
-Environment variables (with defaults in apps/server/config.js):
-
-- `DOMAIN` (default: localhost)
-- `PORT` (default: 5337)
-- `DATA_FILE_PATH` (default: `./data/subscriptions.json`)
-- Resource limits: MAX_RESOURCE_SIZE, REQUEST_TIMEOUT, etc.
-
-### Data Storage
-
-State is persisted to a JSON file (default `./data/subscriptions.json`) managed by services/json-store.js. The store loads into memory at startup and flushes atomically on an interval and at shutdown. No external database is required.
-
-### Testing
-
-- End-to-end tests live in `apps/e2e/test/` (separate workspace package, `@rsscloud/e2e`)
-- Tests use Mocha/Chai, orchestrated via `apps/e2e/docker-compose.yml`
-- Mock servers spin up on ports 8002/8003; SSL certs in `apps/e2e/test/keys/`
-- Server-internal helpers used by tests (RPC builders, dayjs wrapper, init-subscription, config) are duplicated under `apps/e2e/test/helpers/` to keep the suite decoupled from `apps/server` internals
-
-## Commits and Releases
-
-This project uses [Conventional Commits](https://www.conventionalcommits.org/) enforced by commitlint via husky git hooks.
-
-### Commit Format
-
-```
-type: description
-
-[optional body]
-```
-
-### Commit Types
-
-**Trigger releases:**
-
-- `fix:` - Bug fixes → patch release
-- `feat:` - New features → minor release
-- `feat!:` or `BREAKING CHANGE:` → major release
-
-**No release triggered:**
-
-- `chore:` - Maintenance tasks, dependencies
-- `docs:` - Documentation only
-- `style:` - Code style/formatting
-- `refactor:` - Code refactoring
-- `test:` - Adding/updating tests
-- `ci:` - CI/CD changes
-- `build:` - Build system changes
-
-### Release Workflow
-
-1. Push commits to `main`
-2. release-please automatically creates/updates a Release PR
-3. Review the Release PR (contains changelog and version bump)
-4. Merge the Release PR when ready to release
-5. release-please creates GitHub Release and git tag
+`fix:` → patch, `feat:` → minor, `feat!:` / `BREAKING CHANGE:` → major. Other types (`chore:`, `docs:`, `style:`, `refactor:`, `test:`, `ci:`, `build:`) don't trigger releases.