@jarel/myskills 0.1.0-beta.5 → 0.1.0-beta.6

package/README.md

@@ -27,12 +27,13 @@ Responsibilities:
 - support maintainer/admin workflows through role-gated API calls
 - enroll a personal Codex workspace and execute approved updates with an explicit companion command
 - inspect an explicitly selected local Codex profile with a read-only metadata observation or health report
+- create a dry-run-only work/team bootstrap plan from explicit approved roots and skill selectors
 
 CLI tokens should be stored in the platform secret store where possible.
 
 ## Current Slice
 
-This document describes the beta.5 candidate. Use a CLI built from the same
+This document describes the beta.6 CLI candidate. Use a CLI built from the same
 release as the registry for managed updates and Codex workspace commands. The
 beta.2 visibility compatibility shims remain available for existing clients.
 Source versions and npm publication are separate from hosted deployment; the
@@ -82,6 +83,7 @@ myskills config get api-url
 myskills config set api-url <url>
 myskills config reset api-url
 myskills config list
+myskills bootstrap codex --dry-run --profile work --context <file> [--work-source-root <dir>] [--shared-source-root <dir>] --live-root <dir> --include-slug <slug> [--include-slug <slug>] --output <report.json>
 myskills submit --path <file-directory-or-zip> [--api-url <url>] [--token <token>]
 myskills review submissions [--api-url <url>] [--token <token>]
 myskills review bundle <submission-id> [--platform <name>] [--output <file>] [--api-url <url>] [--token <token>]
@@ -165,7 +167,7 @@ Those operations require the server's current-revision, organization-policy,
 membership, exact-release, limit, idempotency, and MFA checks. This CLI does
 not expose a second policy implementation or write command for them.
 
-## Published And Candidate Channels
+## Published CLI And Local Builds
 
 The published beta channel is installed with:
 
@@ -175,9 +177,10 @@ myskills --version
 myskills login
 ```
 
-At the start of beta.5 delivery, npm's beta tag points to beta.4. Do not assume
-it includes these candidate commands. From this repository, build and run the
-candidate without publishing:
+The expected candidate version is `0.1.0-beta.6`. It includes the beta.5 managed
+update and personal Codex workspace commands plus the dry-run-only work/team
+bootstrap planner. To test repository changes before release, build and run them
+locally:
 
 ```bash
 npm ci
@@ -214,6 +217,43 @@ discarded.
 
 `config get api-url`, `config set api-url <url>`, `config reset api-url`, and `config list` manage the saved API URL. `doctor` checks the CLI version, Node version, resolved API URL, `/health`, auth status, token-store backend, install-directory writability, and `/v1/capabilities`. If the CLI is pointed at the web app instead of the API, or a newer command is sent to an older server, command errors include concrete next steps and `--json` returns structured error codes.
 
+`bootstrap codex --dry-run` is a work/team-only local planner. It requires an
+explicit `work` context, a normalized HTTPS target origin, stable target
+instance/workspace/actor identifiers, explicit source and target trust
+compartments (`work`, `shared`, or `work+shared` for sources, and `work-team`
+for the target), typed `work` and/or `shared` source roots, a target root, and
+a positive `--include-slug` allowlist. The context must approve the computed
+source-root type/digests and target-root digest. Personal, consumer, public,
+and unclassified sources are rejected, and candidates are never selected by
+implicit inventory discovery. A plan accepts at most eight selected candidates;
+each candidate snapshot accepts at most 1,000 entries and 32 nested directory
+levels. A one-skill work-owned canary is supported.
+
+The context JSON must include `profile: "work"`, `targetOrigin`,
+`instanceId`, one `tenantId` or `workspaceId`, `actorId`, the canonical trust
+compartments, `approvedSourceRoots` entries of `{type, identityDigest}`, and
+`approvedTargetRootIdentityDigest`.
+
+The planner reads selected source and target content without network or
+registry access. It opens each selected tree through a bootstrap-owned secure
+snapshot reader, then hashes, parses, scans, and reports only those held bytes.
+It writes only the explicitly requested new private report (`0600`) under a
+user-controlled private parent. Reserved package manifests remain strict:
+invalid or multiple manifests fail closed, and no metadata is relocated. The
+full report contains the work binding, approved root digests, owning package
+contract identifiers, candidate content identities, execution identities, the
+exact target precondition (`absent` or `present-identical` with its expected
+artifact identity), and private snapshots. Terminal output is a redacted DTO
+with counts and digests; it does not contain paths, candidate names, inventory,
+or private identifiers.
+There is no apply, publishing, adoption, or target-write mode in this command.
+`ready` means that the held snapshot passed deterministic checks only. It is
+not approval to apply. Sensitive configuration and credential paths are
+excluded before content enters the report, and heuristic scan-clean never
+replaces explicit human content review. Any future executor must repeat the
+retained source/target identity check immediately before its first write
+(compare-and-swap) and require that review at that boundary.
+
 `validate`, `scan`, and `submit` read one bounded snapshot of the local package.
 `submit` sends those same validated and scanned text entries for directory and
 ZIP inputs. Authors can inspect and withdraw submissions; maintainers fetch the