n-seo 0.1.0 → 0.1.1

package/README.md

@@ -1,6 +1,10 @@
 # n-seo
 
-**An SEO, self-hosted.** Website: https://en-dash-consulting.github.io/n-seo/ · From the makers of [n-dx](https://n-dx.dev).
+**An SEO, self-hosted.** Website: https://n-seo.dev/ · From the makers of [n-dx](https://n-dx.dev).
+
+[![npm](https://img.shields.io/npm/v/n-seo)](https://www.npmjs.com/package/n-seo)
+[![CI](https://github.com/en-dash-consulting/n-seo/actions/workflows/ci.yml/badge.svg)](https://github.com/en-dash-consulting/n-seo/actions/workflows/ci.yml)
+[![license](https://img.shields.io/npm/l/n-seo)](LICENSE)
 
 A local-first control plane for growing organic traffic to your own sites —
 classic search (SEO), answer engines (AEO) and AI assistants that cite sources
@@ -24,16 +28,35 @@ It runs on hardware you control, on a schedule, and shows you the result on a da
 
 ## Quickstart (5 minutes, no Google setup)
 
+```sh
+npm install -g n-seo
+n-seo init my-sites && cd my-sites
+n-seo demo          # a synthetic dataset for example.com
+n-seo start         # dashboard → http://localhost:4600
+```
+
+Open http://localhost:4600. Every page is populated from the demo data, so you
+can see what the tool does before you connect anything. `n-seo demo --clean`
+removes it.
+
+Prefer not to install globally? `npx n-seo init my-sites` works the same way.
+
+<details>
+<summary>Or run it from a clone, if you want to change the engine itself</summary>
+
 ```sh
 git clone https://github.com/en-dash-consulting/n-seo.git
 cd n-seo
 npm install
-npm run demo        # writes a synthetic dataset for example.com under data/
-npm start           # dashboard → http://localhost:4600
+npm run demo
+npm start
 ```
 
-Open http://localhost:4600. Every page is populated from the demo data, so you
-can see what the tool does before you connect anything.
+In this mode the config, queue and data live inside the checkout. That is the
+right shape for hacking on n-seo; for running it, the instance layout above
+keeps your files separate from the engine so upgrades are a reinstall rather
+than a merge. See [docs/INSTANCE.md](docs/INSTANCE.md).
+</details>
 
 ## Connect your real sites
 

package/docs/RELEASING.md

@@ -139,6 +139,27 @@ workflow also deliberately omits `registry-url` from `setup-node`, because it
 writes an `.npmrc` auth line interpolating `NODE_AUTH_TOKEN`, and an empty
 value there produces the same misleading 404.
 
+## Approving a staged release
+
+The trusted publisher is configured to allow `npm stage publish` only, so the
+workflow submits a version and stops. It is not on the registry until a human
+approves it with 2FA. That is deliberate: a compromised runner or a stray tag
+cannot put code on npm that other people's machines will then execute.
+
+After the release run goes green:
+
+```sh
+npm stage list n-seo          # the stage id
+npm stage view <stage-id>     # inspect exactly what CI built
+npm stage approve <stage-id>  # 2FA; now it is live
+```
+
+`npm stage reject <stage-id>` throws it away. The package's Staged Packages
+tab on npmjs.com does the same thing in a browser, which is easier if your
+second factor is a passkey rather than an authenticator app.
+
+The workflow's run summary prints these commands with the version filled in.
+
 ## Verify what was published
 
 Do not trust the workflow's own output. Install from the registry, into an

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "n-seo",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Local-first SEO / AEO / GEO control plane: pulls Search Console + GA4, probes your sites, and turns the data into a ranked action queue you can act on without an agency.",
   "license": "MIT",
   "author": "En Dash Consulting (https://endash.us)",
-  "homepage": "https://en-dash-consulting.github.io/n-seo/",
+  "homepage": "https://n-seo.dev/",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/en-dash-consulting/n-seo.git"