humanish 0.15.2 → 0.15.3

package/docs/ramp/README.md

@@ -2,9 +2,10 @@
 
 Status: public-safe contributor and agent ramp.
 
-Current safety state: `0.15.1` (2026-07-14). Managed run and output paths bind
-to validated physical filesystem identities. Stored provider IDs are evidence,
-not cleanup authority. The bundled OSS meta-lab is dry-run only until
+Package/source version in this tree: `0.15.3` (2026-07-14). The containment boundary introduced in
+`0.15.1` remains in force: managed run and output paths bind to validated
+physical filesystem identities, and stored provider IDs are evidence, not
+cleanup authority. The bundled OSS meta-lab is dry-run only until
 repository-derived instructions have an isolated credential boundary.
 
 Use this page when you are starting cold on `humanish`. It is meant to be
@@ -69,13 +70,22 @@ Implemented:
 - first-class lab manifest resolution through `humanish/labs/*.yaml` and
   ignored `.humanish/labs/*.yaml` overlays — `humanish.lab.v2` compositions
   (`src/lab-config.ts`), one engine, no hardcoded lab kinds;
-- a pluggable actor registry with four registered actors
-  (`src/actor-registry.ts`); on the computer-use routes `actors[0].type` is a
-  real dispatch key;
+- a first-party actor registry with six registered descriptors
+  (`src/actor-registry.ts`); `actors[0].type` is a real dispatch key on the
+  computer-use, scripted-browser, and terminal-product routes;
 - a computer-use route and clone subject provider: `subject.source: app-url`
   drives a lab-owner loopback app in a hosted desktop, and `subject.source:
   clone` + `serve` clones, installs, and serves a real app in-sandbox from
   config before the actor drives it (`src/cua-actor-lab.ts`);
+- six declared subject sources: `this-repo` (dry-run-only), `clone`, `app-url`,
+  `local-app` (library-assisted, in-process, no desktop), `terminal-product`,
+  and `local-tree`; each route fails closed on unsupported combinations;
+- bounded per-lane-world fan-out (`actors[0].count`, `lanes[]`, or `roster[]`),
+  backed by deterministic and kept live proof;
+- sequential/concurrent single-origin shared-world execution: sequential has
+  deterministic proof, while concurrent has deterministic and kept live proof;
+- `subject.source: local-tree`, which packages one selected working tree with a
+  content pin before using the same provision-and-serve path as clone subjects;
 - containment checks for managed run storage, Observer and feedback reads,
   actor artifacts, lab discovery, Git metadata, and source archives;
 - an OSS meta-lab dry-run contract and a separate disposable public-repo OSS
@@ -85,16 +95,25 @@ Implemented:
 
 Still not good enough:
 
-- live `--app-url` browser proof now supports app-specific executable
-  `browser.steps` in `humanish/scenarios/*.yaml`, with headed provider-backed
-  public proof against two app/tool targets;
-- live PTY and Codex UI lanes need stronger completion health;
+The [current proof-roadmap checkpoint](https://github.com/danielgwilson/humanish/blob/main/docs/goals/proof-roadmap/README.md)
+supersedes implementation-status phrases in the immutable 2026-06-10 roadmap
+packet without changing its success standard.
+
+- capability receipts are not adopter replacement: no first-party deletion
+  branch has yet removed a bespoke generic harness while preserving
+  decision-equivalent proof;
+- the six actor descriptors are a closed first-party union, not a supported
+  out-of-tree actor-registration API;
+- run storage and provider-resource lifecycle logic still spans several routes
+  instead of one `RunStore` and `ResourceLease` boundary;
+- multi-origin shared-world is a ratified design direction, but remains
+  unimplemented and gated on a real adopter proving the need;
 - live OSS meta-lab execution remains disabled until repository-derived
   instructions have an isolated credential boundary; historical headed-lane
   evidence does not make the current entrypoint available;
-- Observer evidence has real screenshots/traces for browser app proof; richer
-  multi-step product journeys and broader multi-persona matrices remain the next
-  gap.
+- the README hero is a shipped, synthetic four-lane technical sample. It is not
+  proof of a real application study; a legible real-application capture remains open
+  product proof.
 
 ## First Commands
 

package/docs/release/open-source-readiness.md

@@ -81,7 +81,8 @@ from a fresh clone:
 - history scans have no private upstream system names, absolute maintainer paths,
   secret patterns, or generated runtime bundles;
 - reachable commit author and committer emails are GitHub noreply-style
-  addresses or explicitly approved public maintainer emails;
+  addresses (including GitHub's documented `ID+USERNAME` and username-only
+  forms) or explicitly approved public maintainer emails;
 - GitHub issues, PRs, labels, and project fields have been scanned or rewritten
   for public-safe language.
 
@@ -172,8 +173,8 @@ order is load-bearing (the OIDC binding is exact owner/repo + workflow path):
 A tag pushed before steps 1-2 fails auth (OIDC repository claim mismatch) or
 provenance validation (package.json repository.url vs actual workflow repo).
 
-Trusted Publishing should be configured for GitHub Actions before cutting the
-next tag:
+Trusted Publishing is configured for GitHub Actions. Verify these exact binding
+fields before each tag and re-point them after any repository rename:
 
 - provider: GitHub Actions
 - repository owner: `danielgwilson`
@@ -191,7 +192,7 @@ The workflow uses:
 - `npm publish --access public`;
 - no long-lived npm token secret.
 
-Future automated release flow after trusted publishing is configured:
+Automated release flow:
 
 ```bash
 pnpm release:check

package/docs/release/public-readiness-standard.md

@@ -10,6 +10,7 @@ durable context future contributors and agents need.
 
 - [GitHub Docs: Removing sensitive data from a repository](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository)
 - [GitHub Docs: Setting your commit email address](https://docs.github.com/en/account-and-profile/how-tos/email-preferences/setting-your-commit-email-address)
+- [GitHub Docs: Email addresses reference](https://docs.github.com/en/account-and-profile/reference/email-addresses-reference)
 - [GitHub Docs: About secret scanning](https://docs.github.com/code-security/secret-scanning/about-secret-scanning)
 - [GitHub Docs: About push protection](https://docs.github.com/en/code-security/concepts/secret-security/about-push-protection)
 - [npm Docs: package.json files field](https://docs.npmjs.com/cli/v11/configuring-npm/package-json/#files)
@@ -103,7 +104,11 @@ Noreply commit emails are preferred for privacy and consistency.
 
 Allowed commit metadata:
 
-- GitHub noreply addresses.
+- GitHub's two documented personal-account noreply forms:
+  `ID+USERNAME@users.noreply.github.com` and
+  `USERNAME@users.noreply.github.com`. The username-only form remains valid for
+  accounts using GitHub's pre-July 18, 2017 privacy form.
+- `github-actions[bot]@users.noreply.github.com` for GitHub Actions commits.
 - `noreply@github.com` for GitHub-generated commits.
 - Explicitly approved public maintainer emails.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "humanish",
-  "version": "0.15.2",
+  "version": "0.15.3",
   "description": "Open-source-safe CLI for persona simulation, observer review, and public-safe feedback drafts.",
   "author": "Daniel G Wilson <daniel@danielgwilson.com>",
   "keywords": [