m038andClaude Opus 4.8
dcf9c13455
Once user/env/<host>/ exists, Grav Admin saves ALL config (system + plugin) into that env tree, not user/config/ — so prod's git-sync.yaml lives at the env path, and Admin-on-server config edits are server-only (not committed, not synced). Documented the footgun in CLAUDE.md §1 (session-loaded) and rewrote git-sync-notes.md: env-path location, v3.4.4 folders format, gitignore table (incl. versions.yaml + security-private.php TODO), and fresh-server enable procedure. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Np4cMQLF77i664CAQXySzU
docs/
If you're Mischa
Doing something operational? → guides/
- Posting a journal entry
- Managing GPX files
- Switching to a new trip
- Rebuilding local dev from scratch
Checking project status? → working/
Design or architecture decisions? → reference/
If you're Claude
Always-loaded project rules → CLAUDE.md (repo root)
Active specs and plans → working/specs/ and working/plans/
Stable facts → reference/
Raw research input → research/