chore: rename the imported template to memento
Takes over the identity the template left generic. The application name becomes Memento in the browser title, the shell header and the home page, in both the Korean and English catalogs. The browser storage namespace moves from `ca-frontend` to `memento`, which also moves the OPFS root directory, its mutation lock and the journal metadata prefix. Nothing is migrated, because this repository has never been deployed and so no origin holds data under the old prefix. The tests that assert those key strings move with them. Release provenance needs no edit here: the builder and verifier ids are derived from the `name` in package.json upstream, so changing that one line renames them too. The template name is left alone in docs/, where it is part of the record of work that actually happened in that repository, and in the secret scan tool id, which is an internal identifier matched by a validator on both sides rather than a product name. README.md now describes this repository and, more importantly, records how to merge from upstream and exactly which files carry a memento value and will therefore be where conflicts land. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
6a30db2550
commit
c7caeefd06
@@ -62,7 +62,7 @@ describe("production runtime application tree", () => {
|
||||
|
||||
expect(
|
||||
await screen.findByRole("heading", {
|
||||
name: "Clean Architecture Frontend",
|
||||
name: "Memento",
|
||||
}),
|
||||
).toBeVisible();
|
||||
expect(
|
||||
|
||||
Reference in New Issue
Block a user