Rename package and establish version 1.0.0 (#71)

* Initial plan

* Wire package metadata into About app

Co-authored-by: mroxso <24775431+mroxso@users.noreply.github.com>

* Complete About version test wiring

Co-authored-by: mroxso <24775431+mroxso@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: mroxso <24775431+mroxso@users.noreply.github.com>

docs/README.md

@@ -11,6 +11,7 @@ decisions were taken; these documents describe how it actually works.
 | [`apps.md`](./apps.md) | The app registry, the contract every app implements, and how to add one |
 | [`nostr.md`](./nostr.md) | Data access, relay hints, and the rules for rendering untrusted content |
 | [`styleguide.md`](./styleguide.md) | Design tokens, materials, typography, motion, and the layout rules for app content |
+| [`versioning.md`](./versioning.md) | The package version source and release workflow |
 
 ## Layout of the custom code
 

docs/versioning.md

@@ -0,0 +1,17 @@
+# Versioning and releases
+
+`package.json` is the authoritative source for the LAYER.systems package name and
+semantic version. The About app imports that metadata directly, so local and
+production builds display the same version.
+
+## Preparing a release
+
+1. Run `npm version patch`, `npm version minor`, or `npm version major` from the
+   repository root. This updates `package.json` and `package-lock.json`, creates
+   the matching git commit, and creates a version tag.
+2. Run `npm run test` and verify the version in the About app.
+3. Push the commit and tag to publish the release.
+
+The first tracked release is `1.0.0`. Use semantic versioning for all subsequent
+releases: patch for backwards-compatible fixes, minor for backwards-compatible
+features, and major for breaking changes.