fix(website): architecture page scroll + collapse Superpowers KeyPoints (#212)

**Architecture page:** the outer wrapper used `flex h-screen flex-col`,
which forced a viewport-locked container inside the root layout's
header/main/footer stack. That created nested scrolling and made the
footer feel wonky once you reached it. Drop the h-screen wrapper,
size the iframe to `h-[calc(100svh-8rem)]` so it sits naturally in
the page flow, and let the footer appear below.

**KeyPoints collapse:** the three-bullet version was really one idea
split awkwardly — all three bullets were saying 'these are different.'
Collapse into two distinct per-project bullets that each cover both
shape (library vs orchestrator) and target (assisted execution vs
dark factory). This change was lost between push and merge on #211.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: jwaldrip

website/app/studios/[slug]/architecture/page.tsx

@@ -34,7 +34,7 @@ export default async function StudioArchitecturePage({ params }: Props) {
 	if (!studio) notFound()
 
 	return (
-		<div className="flex h-screen flex-col">
+		<>
 			<nav className="flex flex-wrap items-center gap-2 border-b border-stone-200 bg-white px-4 py-2 text-sm dark:border-stone-700 dark:bg-stone-900">
 				<Link href="/studios/" className="text-stone-500 hover:text-stone-900 dark:text-stone-400 dark:hover:text-white">
 					Studios
@@ -52,8 +52,8 @@ export default async function StudioArchitecturePage({ params }: Props) {
 			<iframe
 				src={`/prototype-stage-flow.html?studio=${slug}`}
 				title={`${titleCase(studio.name)} architecture`}
-				className="flex-1 w-full border-0"
+				className="block w-full border-0 h-[calc(100svh-8rem)]"
 			/>
-		</div>
+		</>
 	)
 }

website/content/blog/superpowers-and-haiku.mdx

@@ -21,10 +21,9 @@ People keep asking us where H·AI·K·U fits relative to it, and the honest answ
 
 The short version, for people who want to leave now and not read the rest:
 
-<KeyPoints title="Three things worth saying up front">
-  1. **Superpowers is a skills library. H·AI·K·U is an orchestrator that hands the agent one step at a time from a plan kept on disk.** Same problem space, two honest bets about how to tame it.
-  2. **Superpowers is built around disciplined assisted execution.** The human is in the loop throughout — brainstorm, plan, per-task review, code review — and that continuous partnership is the point.
-  3. **H·AI·K·U is built around a spec that *can* run as dark as you want it to.** The human works hard upstream so execution *can* go [lights-out](/blog/dark-factories-and-the-loop), and per-stage autonomy controls let you keep as much supervision as the work calls for. Dark factory is the ceiling, not the mandate.
+<KeyPoints title="Two bets, two architectures">
+  1. **Superpowers is a skills library built for disciplined assisted execution.** Each skill is a self-contained document the agent loads and runs; the human stays in the loop throughout — brainstorm, plan, per-task review, code review. Continuous human partnership *is* the product.
+  2. **H·AI·K·U is an orchestrator that hands the agent one step at a time from a plan kept on disk, built for a spec that *can* run as dark as you want it to.** The human works hard upstream so execution *can* go [lights-out](/blog/dark-factories-and-the-loop), with per-stage autonomy controls to keep as much supervision as the work calls for. Dark factory is the ceiling, not the mandate.
 </KeyPoints>
 
 Different targets, different architectures. Everything else below is commentary on that.