Repository navigation
Home: new top - hero rewrite and consumer how-it-works [MICHAEL 2026-10-14] - #180
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1ddc5010d9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| after: | ||
| " - write it on anything with a marker, and scan it to open its digital record. The “zz” ends tell our scanner exactly where to look, just like the three corner dots on a QR code.", |
There was a problem hiding this comment.
For every visitor to the new home page, this now says they can “scan it to open” a record and refers to “our scanner,” although the canonical capability boundary says typed lookup is the only implemented path and on-device recognition is not built (docs/SPEC.md:59). This presents planned functionality as currently usable; retain an explicit future/prototype qualification until the camera reader actually ships.
AGENTS.md reference: AGENTS.md:L32-L37
Useful? React with 👍 / 👎.
| export const consumerHow = { | ||
| eyebrow: "Physical-to-digital addressing", | ||
| heading: "Skip the printer. Grab a marker.", | ||
| text: "zzThis is a structurally constrained, human-readable tagging protocol. By bounding ordinary words with a “zz” prefix and suffix, we turn handwriting into a highly secure, scannable data link, from austere environments and logistics to everyday tracking.", |
There was a problem hiding this comment.
Calling the link “highly secure” is unsupported: the accepted product spec explicitly says the codebook is unvalidated and recognition and resolver security are untested (docs/SPEC.md:63, docs/SPEC.md:77-79). Bounding ordinary words with zz only frames the identifier and does not establish security, so this prominent consumer copy makes a claim the repository has no evidence for; remove it or replace it with qualified, validated wording.
AGENTS.md reference: AGENTS.md:L32-L37
Useful? React with 👍 / 👎.
| <div class="hero__photos"> | ||
| {hero.photos.map((photo) => ( | ||
| <img |
There was a problem hiding this comment.
These images are rendered without any visible status label even though the Kathy found-dog set is classified as concept imagery (docs/SPEC.md:66,83) and the marketing requirements mandate one label above every grouped concept gallery (specs/001-marketing-site/spec.md:73). Because the phone image depicts a successful scan and “Record found” while recognition is not implemented, omitting the label makes the mock workflow appear real; add the required grouped-gallery concept label.
AGENTS.md reference: AGENTS.md:L10-L15
Useful? React with 👍 / 👎.
| "Barcodes made things scannable. zzThis makes things readable-writable - and smart.", | ||
| subline: "Write a code on a thing; type it to find its record.", | ||
| eyebrow: "The next evolution of the barcode", | ||
| title: "A barcode/QR code you can write by hand", |
There was a problem hiding this comment.
The accepted marketing spec still requires the previous H1 character-for-character and defines the existing Home sequence (specs/001-marketing-site/spec.md:31-33), while this commit adds only an intent marked Status: draft and immediately changes both implementation and regression tests. Landing this leaves the tested product contract contradicting the authoritative spec; promote and update the spec through the required intent/spec sequence before replacing the H1, or retain the specified copy.
AGENTS.md reference: AGENTS.md:L10-L15
Useful? React with 👍 / 👎.
…10-14] Eyebrow, new headline "A barcode/QR code you can write by hand", the barcode/QR comparison sub-headline with zz-Kathy-found-dog-zz in accent mono, the two hero buttons with How it works first, two Kathy photos, roadmap caveats dropped from the hero body. New "consumer" block under the hero (Physical-to-digital addressing; Skip the printer. Grab a marker.; three steps; no button). Home "How it works" heading becomes "How it works - field". Hero tests move to tests/hero.test.ts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016ZYdSC2Qomx979pDmU5GAS
1ddc501 to
9b6c118
Compare
2 participants
Applies Danny's replacement of Michael's 2026-10-14 home-top patch (
git am --3way) on latestmain.Changes
zz-Kathy-found-dog-zzin accent mono, two Kathy photos (new webp images inpublic/images/hero/).tests/content.test.tsto newtests/hero.test.ts, including a button-order assertion.intent/2026-10-14-michael-home-top.md.Conflict resolution
src/content/hero.ts: took the patch's hero title/subline/paragraph over main's Q62 headline.tests/content.test.ts: kept main's destructuring, droppedfeatured, heroand the hero describe block (moved to hero.test.ts).tests/hero.test.ts: updated the featured-statement expectation to main's current (caveated)featured.text; featured copy unchanged.Results (Node 22.23.2)
npm ci✅ ·npm test✅ (100% coverage) ·npm run lint✅ ·npm run typecheck✅ ·npm run build✅