@karaoke-cms/assert-privacy 0.9.2 → 0.9.5

package/README.md

@@ -2,20 +2,20 @@
 
 Post-build privacy gate for karaoke-cms. Scans the built `dist/` directory and fails if any unpublished vault content has leaked into the output.
 
-## Where it belongs
+## Usage
 
-`packages/assert-privacy/` in the monorepo. Runs as a CI step after `astro build`:
+Runs automatically as a CI step after `astro build`:
 
 ```yaml
 # .github/workflows/deploy.yml
-- run: pnpm build
+- run: npm run build
 - run: node scripts/assert-privacy.js dist
 ```
 
-It is also callable directly:
+Or manually:
 
 ```bash
-node node_modules/.bin/assert-privacy dist/
+node scripts/assert-privacy.js dist
 ```
 
 ## What it does
@@ -24,18 +24,14 @@ Walks every `.html` file in the build output and checks:
 
 - No content from unpublished vault entries (those without `publish: true`) appears in any page
 - The RSS feed at `dist/rss.xml` is well-formed XML
-- No internal draft markers or handbook content leaked into production HTML
+- No handbook content leaked into production HTML
 
 Exits with code 1 and a clear error message if a violation is found, blocking the deploy.
 
 ## Status
 
-**Stub** — the package entry point (`bin/assert-privacy`) is declared but the implementation has not yet been migrated from `apps/template/scripts/assert-privacy.js`. Until migration is complete, use the script directly from your project's `scripts/` directory.
+**Stub** — the package placeholder is installed by scaffolded projects. The implementation lives at `scripts/assert-privacy.js` in your project directory.
 
-The canonical implementation is at `apps/template/scripts/assert-privacy.js` in this monorepo and at `scripts/assert-privacy.js` in scaffolded projects.
+## What's new in 0.9.5
 
-## How it changes the behavior of the system
-
-- This is the last line of privacy defense before content reaches the CDN. The Astro content filter (`publish: true` in `makeCollections()`) prevents unpublished content from entering the build graph. This package verifies the output, catching edge cases like content injected via wikilinks or manually added pages.
-- In CI, a failed assert blocks the Cloudflare Pages deploy entirely.
-- Running it locally after `pnpm build` is the recommended way to verify privacy before pushing.
+No user-facing changes in this release — version bumped for lockstep with the monorepo.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@karaoke-cms/assert-privacy",
   "type": "module",
-  "version": "0.9.2",
+  "version": "0.9.5",
   "description": "Post-build privacy gate for karaoke-cms",
   "keywords": [
     "astro",
@@ -9,6 +9,6 @@
     "privacy"
   ],
   "scripts": {
-    "test": "echo \"No tests yet — source lives in apps/template/scripts/\""
+    "test": "echo \"No tests yet — source lives in apps/website/scripts/\""
   }
-}
+}