thinkpool-pair 0.7.402 → 0.7.404

package/README.md

@@ -206,17 +206,6 @@ The report lists configured project directories, local bridge records, known
 outbound domains, remote storage categories, and the report’s limits. It does
 not print provider keys, refresh tokens, or bridge private keys.
 
-To try thinkpool without pointing an agent at a real repository, create the
-fixed disposable sample under the bridge’s local state directory:
-
-```bash
-npx thinkpool-pair@latest demo-project
-```
-
-The command installs no dependencies, changes no Git repository, and never
-overwrites an existing sample file. It prints the exact folder and next step.
-Run it again to restore any missing sample files while preserving your edits.
-
 Structured session state is stored below `~/.thinkpool-pair/` so an agent lane
 can resume after a bridge restart. Protect that directory like other local
 developer credentials and session state.
@@ -310,20 +299,6 @@ npm --prefix bridge run build:package
 node bridge/.publish-package/publish-guard.mjs
 ```
 
-The same checkout can also produce deterministic readable-source evidence:
-
-```bash
-npm --prefix bridge run source:export
-npm --prefix bridge run source:verify
-```
-
-The export includes the bridge runtime allowlist, release tooling, dependency
-lock, per-file SHA-256 values, and an aggregate digest over the release identity
-and ordered file checksums. Publishing refuses source that differs from the
-checked-out commit. The export remains proprietary until Thinkpool, UAB selects
-an OSI licence and authorizes public publication.
-See `public/security/bridge-source.txt` for the current status.
-
 The staging build preserves the runtime module/file graph but removes comments,
 formatting, and local symbol names. It emits no source maps and integrity-binds
 every published file. Raw `npm pack` and `npm publish` from `bridge/` are