@kungfu-tech/buildchain 2.8.7-alpha.1 → 2.8.7-alpha.2

package/README.md

@@ -241,6 +241,7 @@ their own code.
 
 - `buildchain-site.json`
 - `site-manifest.json`
+- `page-registry.json`
 - `cli-registry.json`
 - `workflow-registry.json`
 - `release-model.json`
@@ -251,7 +252,34 @@ their own code.
 
 `buildchain.libkungfu.dev` should render from these package-owned facts, then
 layer presentation around them. The site should not hand-write Buildchain's
-current release mechanics.
+current release mechanics. `page-registry.json` is the complete markdown page
+source for the public site: README homepage content, all packaged `docs/*.md`
+manuals, action READMEs, the Node API package overview, and fixture guides.
+
+## Homepage Content Contract
+
+This README is also the homepage text source for `buildchain.libkungfu.dev`.
+When a site repository consumes the `@kungfu-tech/buildchain` npm package, it
+should use the generated `dist/site/buildchain-site.json` homepage fields
+instead of parsing this README or maintaining separate homepage copy.
+
+The first screen should be derived from:
+
+- Page identity: the top-level heading.
+- Lead: the opening paragraph that defines Buildchain Release Passport.
+- Trust signal: the start of `Install and Verify`, especially passport-first
+  binary verification.
+- Use signal: the start of `Use Buildchain`, especially the reusable workflow
+  and action surfaces.
+
+The package-owned site bundle exposes ordered `homepage.sections`,
+`homepage.displayPlan`, `homepage.rendererContract`, and a complete
+`pages` collection mirrored from `page-registry.json`. A site renderer may adapt
+layout, navigation, typography, examples, and visual assets, but it should not
+maintain separate wording for Buildchain's release mechanics, workflow surface,
+operation manuals, Node API overview, fixture guides, or release-passport trust
+model. Renderer-contract text is machine/implementation metadata, not ordinary
+homepage content.
 
 ## Local Verification
 

package/dist/site/agent-index.json

@@ -3,6 +3,7 @@
   "contract": "kungfu-buildchain-site-agent-index",
   "readOrder": [
     "site-manifest.json",
+    "page-registry.json",
     "product-mechanism.json",
     "release-model.json",
     "cli-registry.json",

package/dist/site/artifact-schemas.json

@@ -15,6 +15,7 @@
   "site": [
     "buildchain-site.json",
     "site-manifest.json",
+    "page-registry.json",
     "cli-registry.json",
     "manual-registry.json",
     "node-api-registry.json",

package/dist/site/buildchain-contract.json

@@ -4,7 +4,7 @@
   "product": {
     "name": "Buildchain",
     "package": "@kungfu-tech/buildchain",
-    "version": "2.8.7-alpha.1",
+    "version": "2.8.7-alpha.2",
     "repository": "https://github.com/kungfu-systems/buildchain"
   },
   "majorLine": "v2",
@@ -320,7 +320,7 @@
         "manual entries carry source file digests so downstream sites and agents can detect stale hand-written documentation"
       ],
       "breakingDigest": "sha256:7d0d2819e3a3e72989d9c57b5efe9d0bc0a79bc0f2c82a0c7b9d6c5a211a91f2",
-      "auditDigest": "sha256:d5288916e9e83d773188f40713ade69e9ba8418886205727c2290aca512dda0f"
+      "auditDigest": "sha256:65236c3c8d0558544f084ebffdfca2e811fb3d05695faa0d560ce4657c8d7285"
     },
     {
       "contractVersion": 1,
@@ -342,9 +342,9 @@
         "agents can discover supported Node APIs without importing internal file paths"
       ],
       "breakingDigest": "sha256:48f925608d3e2131d90936b07dc2a30341204cae3e6e785c0f77d61ad755c945",
-      "auditDigest": "sha256:0660c503639f5ca6d23ba9c7492b31ee9b05f036ffe76ed5dc8b6cb3bfde367b"
+      "auditDigest": "sha256:393f06ac60e0c71254df0bcecde1ed54c1d5f6ecb0a01e87f2d535cb2a90c52c"
     }
   ],
   "compatibilityDigest": "sha256:36421b592a782decbfe31a7d8d42d70ce1100a56a2c4f4a0ccc21f0617dc72bf",
-  "contractDigest": "sha256:2f9b2f7c688818a6255d5f13059eedd0c23059f1daddecafd95ef4b9e60250a0"
+  "contractDigest": "sha256:e64b93abd4ceebe7e4dbeb4e77741c36f20683a2bcc5c38ab5a07b0dcc4f5aa5"
 }