Jan Novak
cf0f176d3f
Stand up the Go project alongside the Python backend so both run
independently during migration. `make web-go` builds and serves on :8080;
`make web-py` (alias: `make web`) keeps the Python side on :5001.
- go/: new module `fuj-management/go` (Go 1.26)
- cmd/fuj: stdlib-flag dispatcher; `server` + `version` work,
fees/reconcile/sync/infer stubbed for M2/M4
- internal/config: env loader mirroring scripts/config.py
- internal/logging: slog setup, level taken from config
- internal/web: net/http ServeMux + request-timer middleware
- build/Dockerfile: golang:1.26 → alpine:3 multi-stage image
- .golangci.yml: govet, staticcheck, errcheck, gofumpt, unused
- Makefile: web→web-py alias; go-build/go-test/go-run/go-lint/web-go
- CI: parallel build-go job in .gitea/workflows/build.yaml (<tag>-go image)
- docs/plans/: M1 kickoff plan + progress tracker (M1 complete)
- .claude/settings.json: gofumpt + golangci-lint permissions
Gate: make go-build ✓ make go-lint ✓ make go-test ✓ curl :8080 ✓
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
53 lines
2.2 KiB
Markdown
53 lines
2.2 KiB
Markdown
# Plan: Document plan-file location convention in `CLAUDE.md`
|
|
|
|
## Context
|
|
|
|
The user wants all plan files (created during Claude Code's plan mode) to live
|
|
inside the project at `docs/plans/`, with a creation timestamp in the filename.
|
|
This keeps planning artifacts version-controlled alongside the code, makes it
|
|
easy to see when each plan was drafted, and — critically — needs to be
|
|
discoverable by other contributors who use Claude Code on this repo. So the
|
|
convention belongs in `CLAUDE.md`, not in private agent memory.
|
|
|
|
## Approach
|
|
|
|
1. **Add a new section to `CLAUDE.md`** (placed near the existing "Changelog"
|
|
section, since both are about persisted artifacts that Claude maintains):
|
|
|
|
```markdown
|
|
## Plans
|
|
|
|
When Claude Code's plan mode is used, save the plan file inside the repo at
|
|
`docs/plans/YYYY-MM-DD-HHMM-<slug>.md` instead of the default
|
|
`~/.claude/plans/` location. Get the timestamp with
|
|
`date "+%Y-%m-%d-%H%M"` (matches the changelog convention). The `<slug>`
|
|
should be a short kebab-case summary of the plan's topic.
|
|
|
|
Create the `docs/plans/` directory on first use. Plan files are committed
|
|
to the repo so other contributors can review historical decisions.
|
|
```
|
|
|
|
2. **Create the `docs/plans/` directory** with a `.gitkeep` (or just let it
|
|
appear when the first plan is moved in) so the path exists.
|
|
|
|
3. **Move this current plan** into the new location once plan mode exits:
|
|
`docs/plans/2026-05-03-1200-document-plan-location-convention.md`
|
|
(timestamp will be re-generated with the actual `date` output).
|
|
|
|
4. **No memory entry needed** — the rule lives in `CLAUDE.md` and is loaded
|
|
automatically into every Claude Code session in this repo.
|
|
|
|
## Files touched
|
|
|
|
- [CLAUDE.md](CLAUDE.md) — add the new "## Plans" section.
|
|
- New directory: [docs/plans/](docs/plans/) — created on first use.
|
|
- Move this plan file from `~/.claude/plans/...` into `docs/plans/` with the
|
|
proper timestamped filename.
|
|
|
|
## Verification
|
|
|
|
- `grep -A 5 "## Plans" CLAUDE.md` shows the new section.
|
|
- `ls docs/plans/` lists this plan file with a `YYYY-MM-DD-HHMM-` prefix.
|
|
- Next time plan mode is entered in this repo, the new plan is written to
|
|
`docs/plans/` with a fresh timestamp (verify by re-entering plan mode).
|