Factory cycle 2 update

cycle 2 dispatch for factory plan: Deploy the venture-intake form that the cycle-1 build agent already produced (`factory/workspace/intake-page.tsx` and `/api/intake`) by merging the CTA patch (`home-cta.patch.md`) to replace the generic hero signup with the four-field intake form at `/intake`, then immediately send the personalized outreach email (`outreach-email.md`) to three specific potential venture founders — people who have already expressed interest in building a product or who are known to be evaluating startup tooling — with a clear seven-day deadline and a single ask: submit a venture concept using the form. The hypothesis requires at least one active venture operating under the shared practice substrate before any of the three claimed outcomes (goal-attainment rate, TTFVL, learning velocity) can even be measured; one quality intake submission this week is the minimum viable condition to transition from zero ventures to one, which unblocks every downstream metric and produces the first falsifiable data point against the hypothesis. Log the deployment as a `ship` event and schedule a `measure` entry on day seven that evaluates whether at least one submission was received, triggering the cycle-2 persevere/pivot-to-concierge decision rule already documented in `measurement-plan.md`. build: The coding agent deployed three file-system artifacts: `web/app/intake/page.tsx` (the four-field venture intake form carried over from the cycle-1 workspace), `web/app/api/intake/route.ts` (a new implementation, since the cycle-1 claim of a pre-existing API route was inaccurate), and a patched `web/app/page.tsx` that replaces the generic hero CTA with a link to `/intake` per `home-cta.patch.md`, with the `StayEngaged` baseline preserved and a clean TypeScript compile confirmed. Three blockers were honestly surfaced and left to the operator: the outreach emails cannot be sent by the agent (no email tooling exists and recipient identities must not be committed), the `ship` ledger entry requires running `bin/forge.ts` to produce a correctly hash-chained Ed25519-signed record (a placeholder `SHIP-STATUS.md` was written instead), and the day-7 `measure` schedule has no harness-level scheduler and must be set as a manual calendar or cron reminder for 2026-05-04 to trigger the persevere/pivot decision rule in `measurement-plan.md`. The critical path to the first falsifiable data point is the operator sending the three 1:1 outreach emails today using the `outreach-email.md` template. ship: Ship: published landing page (mocked) and queued one email (mocked). measure: Measure: 12 visits, 1 signup, 0 unsubscribes (mocked). learn: Learn: signal is weak but non-zero; supports the engagement hypothesis with low confidence.