fix(dashboard): replace fabricated stat tile labels with browser-storage truth#233
Merged
operatoruplift merged 1 commit intomasterfrom Apr 28, 2026
Merged
Conversation
The /app dashboard rendered three stat tiles with sublabels that did not match what the code actually does: - Chat sessions tile: "On your computer" - Memories saved tile: "Local, encrypted" Both values come from localStorage (chat-sessions-v2, memory-engine-v1). That data lives in the browser, not on disk in the OS sense, and there is no encryption applied to either. The "encrypted" claim is particularly misleading because the encryption helpers in lib/encryption have no callers from these features. Replace both sublabels with "In this browser", which: - Is literally true (localStorage is browser-scoped) - Doesn't claim cryptographic protection that isn't there - Doesn't imply "your data never leaves the device" — chat prompts are still routed through the AI provider the user picked This matches the honesty positioning sweep landing across the homepage in PRs #227-#232 (Privacy / Compliance / ProblemStatement / Pricing / Comparison / FAQ / CloudVsLocal / dataService / ProductPage / MarketOpportunity). Verification: - pnpm check (4/4: copy-check, capability-check, trust-gate, fabrication-rot-check) - pnpm exec tsc --noEmit (clean)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Apr 28, 2026
operatoruplift
added a commit
that referenced
this pull request
Apr 28, 2026
After the homepage + dashboard + auth + demo + blog honesty sweep landed across PRs #233-#239, this PR institutionalizes the changes in two places so they cannot regress silently: scripts/fabrication-rot-check.mjs: Add 6 anchored patterns (rules 14-20): | Pattern | Retired in | Phrase / location | |---|---|---| | `vault sealed[^a-zA-Z]+memory encrypted` | #235 | HeroAnimation canvas text | | `Encrypted on your computer` | #238 | /security page header | | `Your agent ran locally. Zero cloud. Zero surveillance` | #238 | /demo step-6 | | `${...} deployed locally` | #238 | /agents/builder toast | | `AES-256-GCM Encrypted` | #239 | Security card badge | | `change: ['"]Local, encrypted['"] | 'On your computer'` | #233 | /app dashboard tiles | tests/e2e/consumer-copy.spec.ts: Add 8 banned phrases to BANNED_DEV_PHRASES so the existing consumer-copy regression spec asserts they don't appear in rendered body text on /, /paywall, /pricing, /store, /login, /signup. This complements the build-time grep guards with a runtime check that catches regressions in dynamic content. Combined regression net for retired local-machine claims: - 14 fabrication-rot rules (was 10) -> 20 total rules - 8 banned phrases on consumer-copy.spec.ts asserting against rendered body innerText across 5 routes Verification: - pnpm check (4/4: copy-check, capability-check, trust-gate, fabrication-rot-check; 20 rules across 197 files) - pnpm exec tsc --noEmit (clean)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Test plan