Files
zeekay d6abc60506 Add the iOS lane: hanzo-templates had zero of them
The catalogue shipped 71 web templates and one EMPTY `mobile` repo, so
"build an app" had no starting point on the platform people actually
ship to. This is the iOS lane — Expo/React Native and Flutter for
cross-platform, SwiftUI for native.

The constraint that shaped every file here: an iOS archive needs macOS +
Xcode + a signing identity, and our arc fleet has none. hanzoai has 519
registered runners and every one reports `os: linux`; luxfi has 151, same
story; zooai has none. The only macOS builds in the org today
(hanzoai/world build-desktop.yml) run on GitHub-HOSTED macos-14, which is
exactly what the house CI rule says not to do.

So `hanzo.yml` declares only what a Linux arc runner can genuinely
execute — typecheck + web bundle for Expo, analyze + test + web for
Flutter, `swiftc -parse` for SwiftUI — and the macOS archive lives in a
separate `workflow_dispatch`-only `ios.yml`. A job pinned to a label no
runner advertises would sit queued forever if it fired on push; parking
it is honest, a permanently-yellow check is not. The README of every
template states the gap and the one command that closes it.

Same reasoning on the demos. Expo and Flutter both have a real web
target, so `<slug>.hanzo.app` serves the SAME source the simulator runs.
SwiftUI has no web target, so those two templates ship with no demo link
rather than a screenshot pretending to be one.

Upstreams are permissive only and recorded per template: expo/expo
templates (MIT), flutter/samples (BSD-3-Clause), XcodeGen (MIT).

Second measured gap, found while wiring this up: `hanzo-templates` is not in
arcd's `orgs:` list either (hanzoai, luxfi, zooai, parsdao, zenlm), so the
Linux jobs would queue with no runner too. Both gaps are one installer
re-run, no code change; both are spelled out in every README rather than
left to be discovered on the first red build.

Third gap, found by probing rather than assuming, and FIXED here: every
run in this org died as `startup_failure` with no logs and no annotation.
A bare `runs-on: [self-hosted, linux]` probe queued fine while the same
job importing hanzoai/ci failed identically at @v1 and at a pinned SHA —
so it was never the tag. The org defaulted GITHUB_TOKEN to `read`, and
the reusable declares `permissions: packages: write`; a caller cannot
exceed the org maximum, so GitHub kills the run before creating a job.
hanzo-templates now defaults to `write` like hanzoai/luxfi/zooai, and
runs reach `queued` — the honest state, waiting on gap 2.
2026-07-27 23:25:38 -07:00

37 lines
1.7 KiB
TypeScript

/** Local seed data. Swap `items` for a fetch() against your own /v1 API —
* the screens only depend on the Item shape, not on where it came from. */
export type Item = { id: string; title: string; blurb: string; tag: string; body: string };
export const items: Item[] = [
{
id: 'router',
title: 'File-based routing',
tag: 'expo-router',
blurb: 'Every file under app/ is a route on iOS, Android and web.',
body: 'app/(tabs)/index.tsx is the first tab. app/item/[id].tsx is a dynamic route. Deep links, the browser URL bar and the native stack all resolve through the same tree, so there is one navigation model instead of three.',
},
{
id: 'native',
title: 'Real native views',
tag: 'react-native',
blurb: 'UIView under the hood, not a webview in a jacket.',
body: 'The New Architecture (Fabric + TurboModules) is on by default in app.json. Text, View and ScrollView compile to UIKit on iOS and to DOM on web via react-native-web, from the same source.',
},
{
id: 'ota',
title: 'Ship without the review queue',
tag: 'expo-updates',
blurb: 'JS-only changes go out over the air.',
body: 'Anything that does not add a native module can be published as an update instead of a new build. Native changes still need an archive — which needs macOS. See the README.',
},
{
id: 'web',
title: 'One codebase, three targets',
tag: 'metro',
blurb: 'expo export -p web renders this same screen as static HTML.',
body: 'That is how the live demo of this template works: no second implementation, no marketing mock. What you read here is the app the simulator runs.',
},
];
export const byId = (id: string) => items.find((i) => i.id === id);