Files
lightcraft/plan/lightroom-classic/README.md
T
Andrew FrahnandClaude Opus 5.5 6cbc0eb5a9 Phase 0: configurable brand, MIT licence, plan/ and Immich tracker
- brand.toml is the only place the product name lives; every crate and app
  reads it through dac-brand (env vars with legacy fallback, settings folder
  with copy-only migration, default library, preset extensions, i18n {app})
- cargo xtask brand check|test, run|install|package, docs, rename-crates,
  deny and immich; packaging files are templates rendered from brand.toml
- icons regenerated from brand/icon.svg; upstream branding removed
- MIT licence (segment and fetch stay Apache-2.0); cargo deny licence policy
- clean-room rules in AGENTS.md/CLAUDE.md; docs/upstream-merge.md
- plan/ rebuilt and committed; parity tracker reopens Classic rows, adds
  PLAN.md section 2 rows and the IMM Immich section; plan/immich.md and a
  pinned Immich test server

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-10 10:30:06 +11:00

1.3 KiB

Lightroom Classic reference (our own words)

The behaviour we aim to match, described from public knowledge of how Lightroom Classic works and from the rows of docs/parity.md. Nothing here is copied from Adobe: no help text, screenshots, icons, preset files or menu transcripts. Write every description yourself; when in doubt, describe the behaviour, not the wording.

File What it holds
feature-catalog.md every tracked id (LR-, LRC-, MENU-, KEY-, KEYC-, IMM-) with feature name and tier, generated from docs/parity.md
modules.md per-module behaviour notes: what each module is for, its panels and how they interact
menus.md the menu structure per module, as a map of where commands live
shortcuts.md the Classic keyboard map, grouped, and how it differs from ours today

Private observations (notes taken while running the real application, screenshots for personal reference) go in plan/observations/, which is git-ignored and never published.

Updating the catalog. feature-catalog.md is regenerated from the tracker when rows are added: take each row id, its feature name and its tier, grouped by the tracker's ## sections. The tracker is the source of truth for status.