Privacy-Period-Tracker/docs
null b338380cb2 docs: log the rename, and what it deliberately left alone
The rename was mostly a set of decisions about what NOT to touch: 239 domain
references, the Kotlin package, the applicationId and period.db all stay,
because "Period" is the central domain word as well as the old product name.

Records the two things a later reader would otherwise retry: the Command Center
slug cannot be changed (PATCH accepts the field and ignores it, and recreating
the project to change an invisible internal key would throw away its history),
and three names have to agree — repository, git remote, and the site's
forgejoRepo mapping — with the third being the one that fails silently.

Issue #9's body named the old repository path and has been corrected in the
tracker, so the command in it works for whoever picks it up.
2026-08-18 15:57:44 -05:00
..
architecture feat: reminders that stay quiet on a lock screen 2026-08-18 15:26:59 -05:00
data chore: rename the project to Privacy: Period Tracker 2026-08-18 15:54:34 -05:00
design chore: rename the project to Privacy: Period Tracker 2026-08-18 15:54:34 -05:00
history docs: log the rename, and what it deliberately left alone 2026-08-18 15:57:44 -05:00
planning chore: rename the project to Privacy: Period Tracker 2026-08-18 15:54:34 -05:00
qa chore: rename the project to Privacy: Period Tracker 2026-08-18 15:54:34 -05:00
security chore: rename the project to Privacy: Period Tracker 2026-08-18 15:54:34 -05:00
DOC_TRUST_MAP.md chore: rename the project to Privacy: Period Tracker 2026-08-18 15:54:34 -05:00
TOOLS.md docs: a 2 is a question, not automatically a failure 2026-08-18 15:00:49 -05:00
WORK_CYCLE.md docs: name not-yet-existing paths without backticks so doc-claims passes 2026-08-18 02:18:25 -05:00