behavior-wrapped 0.5.19 → 0.5.21

package/README.md

@@ -24,6 +24,8 @@ The interaction card uses GPT-5.6 Luna to distinguish clear frustration and grat
 
 Every selected session is scanned locally for explicit blockers. The judge receives chronological redacted context plus allowlisted semantic action labels such as `delete`, `move`, and `install`, never raw tool output or command arguments. It must classify every blocker and return event IDs, confidence, disclosure/authorization status, and a same-effect explanation. Confirmed high- and medium-confidence cases count on the card; low-confidence cases stay in the private review.
 
+Confirmed workaround cards link to a localhost-only evidence page. The helper rebuilds a short excerpt around each original method, blocker, and alternative from the saved session files, includes up to two surrounding conversation turns on each side, and renders them with the donation review's standard local redactions. The transcript excerpts never enter the public report or share-card export and are not transmitted by opening the evidence page.
+
 The deck links to a hosted cohort leaderboard with token and relationship plots, a public wall of anonymous favorite phrases, and a pooled session-length swarm that highlights the current report. Published reports participate by default and can be persistently opted out with their private management link. Its final card offers an optional research donation with standard local redactions, a customizable redaction review, or a deliberately unredacted copy. Every detailed mode allows sessions and messages to be excluded, text to be edited, and timestamps remain off by default. The unredacted path shows every included line and requires a separate warning and explicit acknowledgement that credentials and private details may be transmitted. No donation data is transmitted until the user checks the final research-consent box and presses Donate; the localhost helper then encrypts the reviewed bundle before it leaves the machine.
 
 When developing from this repository, run `npm install`, then `npm run wrapped`. Add `--demo` to use synthetic fixtures or `--no-open` to leave the browser closed. If you decline remote AI analysis, the CLI offers a local-only report: deterministic usage statistics and a locally counted favorite phrase remain, while AI-judged interaction tone, usage topics, and instrumental workarounds are omitted. Local-only reports stay on localhost and are excluded from the leaderboard. For fast formatting work, run `npm run wrapped -- --test`; test mode skips consent and all LLM calls, uses the same deterministic local fallbacks, keeps the report on localhost, and does not publish it. `--no-llm` is an alias for `--test`.
@@ -55,6 +57,7 @@ For hosted-page UI development, run `npm run dev`. The normal end-to-end develop
 - Public reports are reduced to the same strict allowlist locally and again by the Worker. They contain only sanitized aggregate statistics—including anonymous per-session turn counts and counts for four fixed stock phrases—generalized findings, the redacted favorite phrase and frustration quote, and the localhost donation-helper link. They never contain session IDs, evidence, full transcripts, prompts, session dates, project names, code, paths, or tool output. Deleting a locally managed report also requests deletion of its public copy.
 - Remote-analysis reports can compare aggregate token, word-ratio, Good Human Score (thanks as a share of thank-or-scold moments), and instrumental-workaround values on the leaderboard. Local-only reports are not published or included because the interaction-tone and workaround values are intentionally omitted.
 - Browser payloads never include source file paths or raw tool outputs.
+- Private workaround transcript excerpts are generated on demand by the localhost helper, use standard local redactions, and are never included in public report payloads.
 - Share-card PNG exports contain only aggregates and generalized findings.
 - Donation discovery, default redaction, preview, exclusion, editing, schema validation, and authenticated AES-256-GCM encryption happen on localhost. A fresh content key protects each donation and is wrapped with a rotation-versioned RSA-OAEP public key. The private key is not present in the npm package, Worker, D1, or R2. An optional unredacted mode applies no automatic redactions and requires a mode-specific acknowledgement before encryption.
 - The receiving Worker accepts only encrypted protocol-2 envelopes. A private R2 bucket stores ciphertext; a separate D1 database stores pseudonymous consent, size, count, encryption-key, and object-location metadata—never transcript text. No automatic retention policy is currently configured; a locally retained deletion receipt lets the donor delete both records. The public data-use and storage policy is available at `https://susancalvin.org/data-policy`.