Files
zooqueenandHanzo Dev ae4c4b3034 Give Blue a voice, a wordmark, and links that resolve
Audio: twenty-eight of the twenty-nine clips carry no audio track, so a
mute switch would have switched nothing. What the site can actually say
out loud is the answer, through the browser's own synthesiser — no
network, no key, 180 voices on this machine. The speaker is the user
gesture browsers require, so reading aloud only ever starts because
someone asked for it, and a new question stops the old one mid-sentence.

Proposal links were broken on every card: zips.zoo.ngo serves them under
/docs/<slug>/ and the generator wrote /<slug>, so all 149 pointed at a
404. Fixed, and both link shapes are now asserted — shape is the part a
test can hold, and it is the part that was wrong.

The reply path had no test at all, which is how the parser went unexamined
while the fabricated fallback hid every failure behind it. It has six now,
against a real streaming body: tokens in order, a frame split across two
reads, keep-alives and non-JSON lines skipped, and a refusal arriving as
its own words rather than as prose. Driven end to end against a stand-in
model, the loop lands: clip swaps to Interest, the caption follows, the
[feeling:] tag stays out of the visible answer, and the answer is spoken.

Look: ZOO LABS reads top left at full weight — the mark left the header
for the bottom right, where a launcher belongs, and puts the cursor in the
question box from anywhere on the site. Zen now comes from @hanzo/font,
which is where the family is authored, rather than two woff2 files copied
into public/.

Also fixed: <Paragraph> inside <Paragraph> put a <p> inside a <p> and
broke hydration on both pages; `'' && <X/>` rendered an empty text node
into a gui View, which warns on every render. Both were reported by the
browser and neither had been read.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-01 12:48:58 -07:00

36 lines
1.7 KiB
JavaScript

// Fails on anything the browser complains about: hydration mismatches, page
// errors, sideways scroll. Screens at the four sizes people actually use.
import { chromium } from 'playwright-core'
const [out, base] = process.argv.slice(2)
const SIZES = [['mobile', 390, 844], ['tablet', 834, 1112], ['laptop', 1440, 900], ['desktop', 1920, 1080]]
const PAGES = [['/', 'ask'], ['/research', 'research']]
const browser = await chromium.launch({ channel: 'chrome' })
const problems = []
for (const [path, label] of PAGES) {
for (const [size, width, height] of SIZES) {
const page = await browser.newPage({ viewport: { width, height } })
const where = `${label}-${size}`
page.on('pageerror', (e) => problems.push(`${where}: ${e.message}`))
page.on('console', (m) => {
const t = m.text()
if (/hydrat|cannot be a descendant|Warning:/i.test(t)) problems.push(`${where}: ${t.slice(0, 150)}`)
if (m.type() === 'error' && !/api\.hanzo\.ai|ERR_FAILED|Failed to load resource/.test(t)) {
problems.push(`${where}: ${t.slice(0, 150)}`)
}
})
await page.goto(base + path, { waitUntil: 'networkidle' })
await page.addStyleTag({ content: 'nextjs-portal{display:none!important}' })
await page.waitForTimeout(900)
await page.screenshot({ path: `${out}/${where}.png`, fullPage: true })
const over = await page.evaluate(() => document.documentElement.scrollWidth - document.documentElement.clientWidth)
if (over > 1) problems.push(`${where}: scrolls ${over}px sideways`)
await page.close()
}
}
await browser.close()
console.log(problems.length ? 'PROBLEMS:\n' + [...new Set(problems)].join('\n') : 'clean: no hydration errors, no page errors, no sideways scroll')