Changed
Changed in fragcap 0.5.0.
The project constitution gains two principles: P-10 (One Path To A Target), which requires every capture target to be created by one operation and stored in one form, and P-11 (The Specification Describes What Shipped), which makes the master specification track the released software.
The master specification now describes shipped reality. It carries an Applies-To field naming the released version it documents, records the v0.2.0 through v0.4.0 release history, retitles version-specific sections version-neutrally, and no longer describes v0.2.0 as an unshipped release.
fragcap run replaces the --hint-db flag (and FRAGCAP_HINT_DB) with --catalog-db and --local-db (and FRAGCAP_CATALOG_DB / FRAGCAP_LOCAL_DB), one per store; doctor now reports both store paths. There is no --hint-db alias.
fragcap now keeps two stores in its per-user data directory: a shipped catalog.db (disposable, replaced wholesale by a future catalog refresh) and a user-owned local.db (where learned launch data accumulates and later user data lives). A catalog refresh never touches local.db. Both are created on first run with no elevation, and resolution consults the local store before the catalog.