@brik64/cli 0.1.0-beta.0 → 0.1.0-beta.1

package/NOTICE

@@ -0,0 +1,17 @@
+BRIK64 CLI Public Beta Notice
+
+Copyright (c) 2026 BRIK64 INC. All rights reserved.
+
+BRIK64 CLI 0.1 public beta is provided for evaluation of local PCD workflows,
+bounded evidence review, and claim-safe project scaffolding. The current public
+beta surface is focused on macOS local CLI usage, package validation, and
+versioned release evidence. Expanded platform support and stronger certification
+surfaces remain gated by the BRIK64 evidence process.
+
+Public product information: https://brik64.com/home-cli
+Documentation: https://docs.brik64.com/cli/install
+Repository: https://github.com/brik64/brik64-cli
+Package: https://www.npmjs.com/package/@brik64/cli
+
+Use, redistribution, commercial use, and derivative works require a separate
+license from BRIK64 unless a later release explicitly states otherwise.

package/README.md

@@ -1,12 +1,76 @@
-# BRIK CLI
+# BRIK64 CLI
 
-This repository is the iteration surface for the BRIK64 CLI.
+BRIK64 CLI is the public beta command-line surface for local BRIK64 project
+workflows. It gives developers a practical way to start working with
+PCD-oriented structure, local evidence review, and claim-safe project scaffolding
+from their own machine.
 
-`brik64-prod` remains the authority for methodology, evidence gates, claim
-boundaries and release certification. This repo is for CLI source, packaging,
-platform builds, local tests and versioned beta artifacts.
+Generated code is easy to ship. Trust is the harder part. BRIK64 CLI is built
+for teams that want software work to carry clearer structure, repeatable
+evidence, and release language that stays aligned with verified artifacts.
 
-Current status: public beta pre-release candidate for `0.1.0-beta.0`.
-Do not claim npm publication, GitHub Release publication, universal platform
-support, N5 authorization, formal certification or production readiness unless
-the corresponding `brik64-prod` release gates and public manifests pass.
+## Status
+
+Current beta: `0.1.0-beta.1`
+
+This beta is intended for evaluation, local workflow trials, package smoke
+testing, and bounded PCD/evidence review. The current public beta surface is
+focused on macOS local CLI usage and developer-facing evidence workflows.
+Broader platform support, stronger certification surfaces, and deeper compiler
+claims remain gated by the evidence process in `brik64-prod`.
+
+`brik64-prod` remains the authority for methodology, release gates, evidence
+contracts, certification boundaries, and public claim authorization. This repo
+contains the CLI source, package metadata, local tests, PCD seed files, and
+versioned beta artifacts.
+
+## Install
+
+```sh
+npm install -g @brik64/cli@beta
+```
+
+After installation:
+
+```sh
+brik --version
+brik help
+```
+
+Public web surface: https://brik64.com/home-cli
+
+Docs: https://docs.brik64.com/cli/install
+
+## What It Does
+
+- Provides the `brik` command for the BRIK64 CLI beta.
+- Supports local PCD-oriented project scaffolding and inspection workflows.
+- Includes seed PCD examples and bounded evidence artifacts for CLI beta review.
+- Keeps evidence boundaries visible as teams move from local workflow to stronger
+  BRIK64 review.
+- Establishes the public package surface for controlled CLI evaluation and future
+  SDK alignment.
+
+## Current Scope
+
+The `0.1.0-beta.1` release is scoped to public beta evaluation. It is centered
+on local developer workflow, macOS package validation, PCD seed material, and
+release evidence review. Production certification, expanded platform support,
+and advanced compiler-methodology claims are promoted only when the matching
+BRIK64 gates and evidence packs authorize that scope.
+
+## Release Evidence
+
+The public beta package is tied to versioned release artifacts, checksums, and
+operator gates. Use the GitHub release assets and checksums to review the exact
+package candidate before treating any install path as authoritative.
+
+GitHub release: https://github.com/brik64/brik64-cli/releases/tag/v0.1.0-beta.1
+
+## Copyright And License
+
+Copyright (c) 2026 BRIK64 INC. All rights reserved.
+
+See `LICENSE` and `NOTICE`. Use, redistribution, commercial use, and derivative
+works require a separate license from BRIK64 unless a later release explicitly
+states otherwise.

package/docs/GITHUB_NPM_PUBLISHING.md

@@ -0,0 +1,67 @@
+# GitHub To npm Publishing Runbook
+
+BRIK64 CLI beta releases should be published from GitHub Actions after the
+package metadata, README, NOTICE, release evidence, and claim-safe copy have
+been reviewed.
+
+## Recommended Path
+
+Use the manual workflow:
+
+```text
+.github/workflows/publish-npm-beta.yml
+```
+
+Inputs:
+
+- `version`: exact `package.json` version, for example `0.1.0-beta.1`.
+- `dist_tag`: normally `beta`.
+- `confirm_public_beta`: must equal `PUBLISH_BRIK64_CLI_BETA`.
+
+Required GitHub configuration:
+
+- Environment: `npm-beta`.
+- Secret: `NPM_TOKEN` with publish rights for `@brik64/cli`.
+- Recommended environment protection: require human approval before publish.
+
+## Workflow Checks
+
+The workflow:
+
+- validates package name and exact version;
+- restricts this lane to `0.1.0-beta.*` versions;
+- runs `npm test`;
+- runs `npm pack --dry-run`;
+- requires `README.md` and `NOTICE`;
+- fails if the version already exists on npm;
+- publishes with public access and the selected dist-tag;
+- verifies npm version metadata and dist-tag after publish.
+
+## Trusted Publishing Upgrade
+
+npm supports Trusted Publishing from GitHub Actions using OIDC. That path reduces
+long-lived token exposure and can generate npm provenance automatically for a
+public package published from a public GitHub repository.
+
+To migrate:
+
+1. In npm package settings, add GitHub Actions as a trusted publisher for
+   organization `brik64`, repository `brik64-cli`, and this workflow.
+2. Keep `permissions.id-token: write` in the workflow.
+3. Test one beta publish from GitHub Actions.
+4. After the trusted publisher works, restrict or revoke traditional npm tokens.
+
+Until the trusted publisher is configured on npmjs.com, keep using `NPM_TOKEN`
+in the protected `npm-beta` GitHub environment.
+
+## Copy Boundary
+
+Release copy should describe beta scope positively:
+
+- local PCD workflows;
+- bounded evidence review;
+- claim-safe project scaffolding;
+- macOS local CLI usage for the current beta;
+- stronger scopes promoted only after matching BRIK64 gates authorize them.
+
+Use `docs/RELEASE_COPY_MANUAL.md` before publishing a new npm beta.

package/docs/RELEASE_COPY_MANUAL.md

@@ -0,0 +1,298 @@
+# BRIK64 CLI Release Copy Manual
+
+This manual standardizes public copy for BRIK64 CLI package pages, GitHub
+releases, changelogs, repository descriptions, and launch snippets. It is built
+for beta releases where public wording must be useful, commercial, searchable,
+and aligned with BRIK64 evidence boundaries.
+
+## Authority
+
+- Product surface: BRIK64 CLI.
+- Current public beta: `0.1.0-beta.1`.
+- Public web surface: https://brik64.com/home-cli
+- Docs: https://docs.brik64.com/cli/install
+- Package: https://www.npmjs.com/package/@brik64/cli
+- Release: https://github.com/brik64/brik64-cli/releases/tag/v0.1.0-beta.1
+- Evidence authority: `brik64-prod` gates, manifests, checksums, and release
+  reports.
+- Implementation surface: `brik64-cli` source, package metadata, tests, PCD seed
+  files, and beta artifacts.
+
+## Voice Standard
+
+BRIK64 release copy should be:
+
+- technically serious;
+- practical for developers;
+- clear about beta maturity;
+- evidence-aligned;
+- commercially legible;
+- confident without overreach.
+
+Prefer scope language over negative disclaimers:
+
+- `current beta scope`;
+- `focused on macOS local CLI usage`;
+- `gated by the BRIK64 evidence process`;
+- `promoted when matching gates authorize the scope`;
+- `release evidence available in attached manifests and checksums`.
+
+## Canonical Package Description
+
+Use this for `package.json.description` and short package surfaces:
+
+```text
+BRIK64 CLI public beta for local PCD workflows, bounded evidence review, and claim-safe project scaffolding.
+```
+
+Alternative short descriptions:
+
+```text
+BRIK64 CLI beta for local project scaffolding, PCD-oriented workflows, and evidence-aware software review.
+```
+
+```text
+Command-line beta for BRIK64 local workflows, PCD seed material, and versioned release evidence.
+```
+
+## Long Description
+
+Use this for release pages, npm README intros, GitHub repository description
+expansion, and docs package cards:
+
+```text
+BRIK64 CLI is the public beta command-line surface for local BRIK64 project workflows. It gives developers a practical way to start working with PCD-oriented structure, local evidence review, and claim-safe project scaffolding from their own machine.
+
+The current beta is focused on macOS local CLI usage, package validation, seed PCD material, and developer-facing evidence workflows. Broader platform support, stronger certification surfaces, and deeper compiler-methodology claims are promoted only when the matching BRIK64 gates and evidence packs authorize that scope.
+```
+
+## GitHub Repository Description
+
+Use one of these as the GitHub repo description:
+
+```text
+BRIK64 CLI public beta for local PCD workflows, evidence review, and claim-safe project scaffolding.
+```
+
+```text
+Public beta command-line surface for BRIK64 local workflows, PCD seed material, and release evidence review.
+```
+
+Recommended repo topics:
+
+```text
+brik64, brik, cli, pcd, evidence, software-trust, developer-tools, public-beta, macos, command-line
+```
+
+## npm Keywords
+
+Use these in `package.json.keywords`:
+
+```json
+[
+  "brik64",
+  "brik",
+  "cli",
+  "pcd",
+  "evidence",
+  "software-trust",
+  "developer-tools",
+  "public-beta"
+]
+```
+
+Optional keywords for later releases, only when the relevant surface exists:
+
+```text
+topology, certification, sdk, macos, linux, windows, compiler, governance
+```
+
+Add platform keywords only when that platform has release evidence.
+
+## SEO Titles And Meta Copy
+
+Homepage/package card title:
+
+```text
+BRIK64 CLI Public Beta
+```
+
+SEO title:
+
+```text
+BRIK64 CLI - Public Beta for Local PCD and Evidence Workflows
+```
+
+Meta description:
+
+```text
+Install the BRIK64 CLI public beta for local PCD-oriented workflows, evidence review, and claim-safe project scaffolding. Current beta focused on macOS local CLI usage.
+```
+
+Social card title:
+
+```text
+BRIK64 CLI 0.1 Public Beta
+```
+
+Social card description:
+
+```text
+A local command-line surface for PCD-oriented project structure, bounded evidence review, and BRIK64 beta workflow evaluation.
+```
+
+## GitHub Release Template
+
+```markdown
+# BRIK64 CLI {{version}}
+
+BRIK64 CLI is the public beta command-line surface for local BRIK64 project workflows. It gives developers a practical way to start working with PCD-oriented structure, local evidence review, and claim-safe project scaffolding from their own machine.
+
+## Beta Scope
+
+This release is intended for evaluation, local workflow trials, package smoke testing, and bounded PCD/evidence review. The current public beta surface is focused on macOS local CLI usage and developer-facing evidence workflows. Broader platform support, stronger certification surfaces, and deeper compiler-methodology claims remain gated by the evidence process in `brik64-prod`.
+
+## Install
+
+```sh
+npm install -g @brik64/cli@beta
+brik --version
+brik help
+```
+
+Public web surface: https://brik64.com/home-cli
+
+Docs: https://docs.brik64.com/cli/install
+
+## What Is Included
+
+- `brik` CLI beta package for local workflow evaluation.
+- PCD seed material for CLI-oriented project structure.
+- Bounded evidence artifacts and release checksums.
+- macOS package validation surface for this beta.
+- Public package/release metadata aligned to BRIK64 claim boundaries.
+
+## Evidence
+
+Use the attached manifests, checksums, and release assets to review the exact package candidate. `brik64-prod` remains the authority for methodology, release gates, evidence contracts, certification boundaries, and public claim authorization.
+
+## Copyright
+
+Copyright (c) 2026 BRIK64 INC. All rights reserved.
+```
+
+## Changelog Template
+
+Use this as the standard changelog text for beta releases:
+
+```markdown
+# Changelog
+
+## {{version}} - {{date}}
+
+### Added
+
+- Published the BRIK64 CLI public beta package surface for local workflow evaluation.
+- Added PCD seed material for CLI-oriented project structure.
+- Added bounded evidence artifacts and release checksums for package review.
+- Added public metadata linking the package, repository, docs, and BRIK64 web surface.
+
+### Changed
+
+- Standardized package and release copy around beta maturity, local developer workflow, and evidence review.
+- Aligned repository and release metadata with BRIK64 claim-safe public wording.
+
+### Verification
+
+- Package smoke tested with `npm pack --dry-run`.
+- GitHub release assets include checksums and manifests for the beta artifact.
+- npm `beta` dist-tag points to the current beta version after publication.
+
+### Scope
+
+This beta is centered on local developer workflow, macOS package validation, PCD seed material, and release evidence review. Expanded platform support and stronger certification surfaces are promoted when the matching BRIK64 gates and evidence packs authorize that scope.
+```
+
+## README Section Order
+
+For npm and GitHub, keep README sections in this order:
+
+1. Product intro.
+2. Status.
+3. Install.
+4. What it does.
+5. Current scope.
+6. Release evidence.
+7. Copyright and license.
+
+The npm README is captured at publish time. Updating README copy in the repo does
+not update an already published package page; publish a new semver version when
+README or metadata must change on npm.
+
+## Copy Rules By Surface
+
+### npm
+
+- Keep the `description` short and searchable.
+- Include `homepage`, `repository`, `bugs`, `author`, `keywords`, `engines`,
+  `publishConfig`, `README.md`, `LICENSE`, and `NOTICE`.
+- Use `--access public` for scoped public packages.
+- Keep `beta` dist-tag for beta releases.
+
+### GitHub Release
+
+- Title format: `BRIK64 CLI {{version}} public beta`.
+- Body should include beta scope, install command, included artifacts, evidence,
+  and copyright.
+- Keep release assets and checksums attached.
+- Use prerelease for beta versions.
+
+### GitHub Repository
+
+- Description should fit one sentence.
+- Topics should be product/search terms, not unsupported platform claims.
+- README must mirror npm package copy.
+- Keep `NOTICE` and `LICENSE` visible at repo root.
+
+### brik64.com / docs
+
+- Link to npm, GitHub release, and docs install page.
+- State the current beta scope positively.
+- Prefer `current support` and `beta scope` over negative disclaimers.
+- Use evidence language when stronger claims appear.
+
+## Claim-Safe Wording Bank
+
+Use:
+
+```text
+public beta
+local workflow evaluation
+PCD-oriented structure
+bounded evidence review
+release evidence
+macOS local CLI usage
+claim-safe project scaffolding
+gated by BRIK64 evidence process
+versioned release artifacts
+checksums and manifests
+```
+
+Keep advanced or platform-specific wording evidence-bound. Platform language should stay scoped:
+
+```text
+current public beta surface is focused on macOS local CLI usage
+```
+
+```text
+Linux and Windows support should be described only after platform-specific gates pass
+```
+
+## Standard Footer
+
+```text
+Copyright (c) 2026 BRIK64 INC. All rights reserved.
+```
+
+Use this footer in package README, release notes, NOTICE, docs cards, and public
+repo descriptions where space allows.

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "@brik64/cli",
-  "version": "0.1.0-beta.0",
+  "version": "0.1.0-beta.1",
   "private": false,
-  "description": "BRIK64 CLI 0.1 public beta scaffold for local PCD workflows and bounded evidence review.",
-  "homepage": "https://docs.brik64.com/cli/install",
+  "description": "BRIK64 CLI public beta for local PCD workflows, bounded evidence review, and claim-safe project scaffolding.",
+  "homepage": "https://brik64.com/home-cli",
   "repository": {
     "type": "git",
-    "url": "https://github.com/brik64/brik64-cli.git"
+    "url": "git+https://github.com/brik64/brik64-cli.git"
   },
   "bugs": {
     "url": "https://github.com/brik64/brik64-cli/issues"
@@ -17,5 +17,38 @@
   },
   "scripts": {
     "test": "bash tests/smoke.sh"
-  }
+  },
+  "author": {
+    "name": "BRIK64 INC",
+    "url": "https://brik64.com"
+  },
+  "keywords": [
+    "brik64",
+    "brik",
+    "cli",
+    "pcd",
+    "evidence",
+    "software-trust",
+    "developer-tools",
+    "public-beta"
+  ],
+  "engines": {
+    "node": ">=20"
+  },
+  "publishConfig": {
+    "access": "public",
+    "tag": "beta",
+    "registry": "https://registry.npmjs.org/"
+  },
+  "files": [
+    "src",
+    "pcd",
+    "docs",
+    "evidence",
+    "packaging",
+    "README.md",
+    "LICENSE",
+    "NOTICE",
+    ".brik/manifest.json"
+  ]
 }

package/tests/.gitkeep

@@ -1 +0,0 @@
-

package/tests/smoke.sh

@@ -1,54 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-ROOT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
-BRIK="$ROOT_DIR/src/brik.js"
-tmpdir="$(mktemp -d)"
-cleanup() { rm -rf "$tmpdir"; }
-trap cleanup EXIT
-
-node "$BRIK" --version | grep -q "BRIK64 CLI 0.1.0-beta.0"
-node "$BRIK" --help | grep -q "status=bootstrap_non_release"
-
-(
-  cd "$tmpdir"
-  node "$BRIK" init
-  test -f .brik/manifest.json
-  test ! -f AGENTS.md
-)
-
-cat >"$tmpdir/program.pcd" <<'PCD'
-program sample
-monomer ADD
-PCD
-
-if node "$BRIK" emit "$tmpdir/program.pcd" >/tmp/brik-emit.out 2>/tmp/brik-emit.err; then
-  echo "emit should require certificate" >&2
-  exit 1
-fi
-grep -q "certificate_required" /tmp/brik-emit.err
-
-node "$BRIK" certify "$tmpdir/program.pcd"
-node "$BRIK" emit "$tmpdir/program.pcd" | grep -q "pcd_sha256="
-
-for target in ts rust python; do
-  out="$tmpdir/out-$target"
-  node "$BRIK" emit "$tmpdir/program.pcd" --target "$target" --out "$out" --tests >/tmp/brik-emit-$target.out
-  grep -q "generated=" "/tmp/brik-emit-$target.out"
-  grep -q "tests=" "/tmp/brik-emit-$target.out"
-done
-
-test -f "$tmpdir/out-ts/program.ts"
-test -f "$tmpdir/out-ts/program.test.ts"
-test -f "$tmpdir/out-rust/program.rs"
-test -f "$tmpdir/out-rust/program_test.rs"
-test -f "$tmpdir/out-python/program.py"
-test -f "$tmpdir/out-python/test_program.py"
-
-if node "$BRIK" emit "$tmpdir/program.pcd" --target go --out "$tmpdir/out-go" --tests >/tmp/brik-emit-go.out 2>/tmp/brik-emit-go.err; then
-  echo "unsupported target should fail closed" >&2
-  exit 1
-fi
-grep -q "unsupported_target" /tmp/brik-emit-go.err
-
-echo "brik64-cli bootstrap smoke: PASS"