One component per file; GAME OVER offers CONTINUE

PRD G1 asks for one component per file. Eight files held two or
three; their eleven extra components move to files of their own,
helpers stay where both sides use them, and an archtest now fails
any file that holds two.

PRD 4.4 and the request say an error always offers CONTINUE.
ErrorState's button read RETRY; it now reads CONTINUE, under the
CONTINUE? countdown, on the crash screen and the lost page alike.

web/tests/smoke.spec.js

@@ -238,13 +238,13 @@ test('resize keeps whole pixels per dot', async ({ page }) => {
   expect(Number.isInteger(s.zoom)).toBe(true)
 })
 
-test('a Go panic shows GAME OVER in pixels; RETRY reloads', async ({ page }) => {
+test('a Go panic shows GAME OVER in pixels; CONTINUE reloads', async ({ page }) => {
   test.info().annotations.push({ type: 'console errors', description: 'the panic is on purpose' })
   await open(page, '#/f/icons')
   await page.evaluate(() => window.__8bitGo.pointer('bogus', 0, 0))
   expect(await texts(page)).toContain('web: unknown pointer kind bogus')
   await expect(page.locator('#over')).toBeHidden()
-  await click(page, 'RETRY')
+  await click(page, 'CONTINUE')
   await page.waitForFunction(() => window.__8bit?.ready && window.__8bit.page() === '/f/icons')
   expect(await texts(page)).toContain('COPY CODE')
 })