@volter/twin-catalog 0.2.41 → 0.2.42

package/catalog.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "sourceCommit": "a4c5e0664985a7f5a173b58cd307b88a7ddd2795",
+  "sourceCommit": "0bf8d1e4abbdf762531c875c432edf9516edf63b",
   "digest": "5103e721dd9632a05ec4d5348d1b9e668ee092b3edf634c0e4b08f08efb76527",
   "versions": [
     {

package/docs/operations.md

@@ -80,6 +80,14 @@ gh workflow run publish.yml --repo "$catalog_repository" --ref main
 
 The workflow verifies admission and protection, then reuses a published version only when source and digest match. It cannot overwrite a conflicting identity. Retain the new receipt and compare registry integrity before calling the upload confirmed. No platform build, candidate test or hosted deployment is part of this job.
 
+The product site is an independent consumer. Its configured operator scheduler runs the site-only
+`apps/www/scripts/refresh.py` command documented in the World website's publishing instructions.
+It installs an exact released index in a disposable directory, retains registry integrity, builds
+and uploads the product site, and confirms the production snapshot. A site refresh does not
+rebuild or release the platform, change an admission, or replace a user's World pin. Hosting
+custody stays with that site operator; this catalog receives no hosting credential. Inspect the
+site publisher's retained receipt and failure logs when the npm snapshot is newer than the site.
+
 ## Recommend, reject or revoke
 
 A moderator rejects a PR with a concrete reason. An unmerged readiness success adds no release to the index.

package/docs/process.md

@@ -230,9 +230,9 @@ historical records. Consumers read `recommendations.json` and `revocations.json`
 release is different from offering it as an install default: pending, rejected, revoked and prerelease versions are
 never automatic selections. A missing or failing assessment is never inferred from a publisher badge.
 
-A future catalog page groups implementations under a vendor, attributes the repository and publisher, and links to
-the immutable version and admission PR/evidence. It can display readiness, support counts, journey failures and replay
-results separately. A contributor sees the PR check, one updated feedback comment, and downloadable workflow artifacts.
+The public catalog groups implementations under a vendor, attributes the repository and publisher, and links to
+the immutable version and admission PR/evidence. It displays release documentation and Setup separately from
+support counts, installed-customer journeys and replay results. A contributor sees the PR check, one updated feedback comment, and downloadable workflow artifacts.
 Readiness checks bind the report digest, workflow run ID and attempt in their external receipt. GitHub may replace
 the display URL and attach a manually dispatched check to an older PR check suite; that display association is not
 the report's source. After authorized merge, publication fetches the exact recorded workflow attempt and requires

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@volter/twin-catalog",
-  "version": "0.2.41",
+  "version": "0.2.42",
   "description": "The moderated twin distribution: approved versions and submission tooling for independent publishers.",
   "type": "module",
   "bin": {
@@ -39,7 +39,7 @@
     "content"
   ],
   "catalog": {
-    "sourceCommit": "a4c5e0664985a7f5a173b58cd307b88a7ddd2795",
+    "sourceCommit": "0bf8d1e4abbdf762531c875c432edf9516edf63b",
     "digest": "5103e721dd9632a05ec4d5348d1b9e668ee092b3edf634c0e4b08f08efb76527"
   }
 }