fix: reconcile cross-surface claim with qualification evidence (accurate, not downgraded)#302
Merged
Merged
Conversation
…ate, not downgraded) The hero over-claimed cross-surface support in unqualified present tense while the qualification-evidence surfaces (status.json, docs what-works-today) record browser as the managed/production substrate and the others as customer-controlled. A buyer reading both downgraded everything. This makes the strongest claim accurate and makes hero, install section, and the on-page cross-surface matrix tell one consistent story, without weakening any claim. - MastHead hero: keep "one governed loop across browser, desktop, RDP, and Citrix" and add the honest mechanism: browser runs in production today; desktop, RDP, and Citrix run through customer-controlled qualification. - InstallSection: same production-vs-qualification framing on the present-tense "records, compiles, replays across ..." line. - ProductStatus (on-page cross-surface section): add the same framing plus a link to the per-surface qualification evidence, so hero -> matrix reads as one narrative (measured, not a reversal). - Pricing Cloud card: add an honest "who it is for" sentence (developers/teams evaluating browser workflows on non-regulated data), consistent with the no-SLA/no-regulated price ladder. No pricing numbers or forms touched. - Footer staleness: the committed fallback snapshot carries an authoring-time timestamp, not a real GitHub observation, so it rendered an ever-growing "snapshot from Nd ago" while the home page (fresh build-time fetch) showed "updated 5m ago". Give the pure-snapshot state a stable "last-known counts" label so freshness reads consistently across pages; live/stale states keep their accurate relative time. Tests and the cypress contract updated. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NyCHrzA1psrKMFfroYbzaM
✅ Deploy Preview for cosmic-klepon-3c693c ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Problem
A diligent buyer read two live URLs that contradicted each other:
status.json/ docswhat-works-todayrecord browser as the managed/production substrate and Windows/macOS/Linux/RDP/Citrix as customer-controlled, with bounded per-surface acceptance evidence (Citrix explicitlyica_hdx_accepted: false, etc.).Reading both, a buyer downgraded everything. Per the founder's rule, this PR does not downgrade the cross-surface story. It keeps the surface-neutral architecture claim and makes the strongest version accurate, so hero → matrix tell one story.
Before → after (no claim weakened, only made accurate + consistent)
Hero (
components/MastHead.js)The cross-surface claim is retained in full; the added sentence is the honest mechanism (the same customer-controlled-qualification framing already used in the docs and
status.json), not a hedge.Install section (
components/InstallSection.js) — same production-vs-qualification framing applied to the present-tense "records, compiles, and replays across browser, Windows, macOS, Linux, RDP, and Citrix" line.On-page cross-surface matrix (
components/ProductStatus.js) — added the same framing plus a link to the per-surface qualification evidence, so a reader moving hero → matrix sees the per-surface acceptance status as the measured backing for the same architecture, not a reversal.Smaller live fixes (in scope)
utils/repositoryStatsView.js): the committed fallback snapshot carries an authoring-time timestamp, not a real GitHub observation, so it rendered an ever-growing "snapshot from Nd ago" while the home page (fresh build-time fetch) showed "updated 5m ago" — inconsistent staleness across pages. The pure-snapshot state now renders a stable, honest "GitHub · last-known counts"; live/stale states keep their accurate relative time. Unit test + cypress contract updated.components/Pricing.js): added one honest sentence — for developers and teams evaluating browser workflows on non-regulated data; regulated data and production SLAs are scoped separately through qualification — consistent with the no-SLA / no-regulated / $500-mo ladder. No pricing numbers or intake/checkout forms touched.Out of scope (untouched)
Case-study files,
/contribute, pricing intake/checkout forms, pricing numbers, and the trust-center SOC 2 statement. Theopenadapt-opsdocs (index.md,what-works-today.md,deployment-matrix.md) already use this exact browser-production / others-customer-controlled framing, so no docs change was needed.Verification
npm run buildgreen (prebuild ran the fullnode --testsuite — 131/131 pass — plus presentation verification, thennext buildsucceeded).🤖 Generated with Claude Code
https://claude.ai/code/session_01NyCHrzA1psrKMFfroYbzaM