feat: rebuild landing page with product evidence

.docs/design-reference-synthesis.md

@@ -0,0 +1,36 @@
+# Design Reference Synthesis
+
+## Purpose
+
+Use `VoltAgent/awesome-design-md` as an unofficial comparative research corpus, never as a drop-in identity. OpenAPI Studio must remain recognizable as itself and must not reproduce proprietary trade dress.
+
+The source documents are community analyses rather than official brand standards; several are explicitly inspired interpretations. Treat every extracted value as fallible and potentially stale.
+
+## Reference Set
+
+- **IBM / HashiCorp:** enterprise grid discipline, explicit surface hierarchy, restrained accents, dense proof.
+- **ClickHouse / Replicate:** memorable single-color identity paired with real technical artifacts.
+- **Vercel / Apple:** controlled typography, clear interaction hierarchy, deliberate whitespace.
+- **Linear / Raycast:** product imagery carries the claim; marketing chrome stays subordinate.
+- **Sanity / Sentry:** strong brand color is balanced by readable dark evidence surfaces.
+- **Stripe:** narrative sequencing and high information clarity without uniform section templates.
+- **Supabase:** code and product proof remain legible, contextual, and close to conversion actions.
+
+## OpenAPI Studio Translation
+
+1. Keep redline as the single identity color; reserve coral, green, and dark tones for semantic contract states.
+2. Make the contract review artifact the visual proof, not decoration.
+3. Use one neutral canvas hierarchy: canvas, dark evidence, hairlines, and one inverse offer.
+4. Keep display type below 76px desktop and 64px mobile. Later-section headings stay below 68px.
+5. At 1440×900 and 2048×1000, the first viewport must show the value proposition, primary CTA, price condition, and complete product artifact.
+6. Body and consequential microcopy never fall below 12px; normal marketing body defaults to 16–20px.
+7. Avoid repeated cards, repeated eyebrow scaffolding, gradients, glass, generic screenshots, and borrowed brand motifs.
+8. Validate the fold separately from full-page rhythm. A full-page screenshot cannot approve conversion visibility.
+9. Resolve IBM density versus Apple spaciousness deliberately: compact above the fold, then add air after the product proof.
+
+## Rejected Imports
+
+- IBM blue, Linear lavender, ClickHouse yellow, Stripe gradients, and Vercel monochrome are brand signatures, not reusable tokens.
+- Apple-scale whitespace without Apple-scale imagery and recognition becomes empty space.
+- Massive editorial display type is inappropriate when it displaces the conversion action.
+- Dark developer-tool styling must remain confined to authentic contract evidence, not become category cosplay.

.impeccable/live/config.json

@@ -0,0 +1,6 @@
+{
+  "files": ["src/routes/__root.tsx"],
+  "insertBefore": "</body>",
+  "commentSyntax": "jsx",
+  "cspChecked": true
+}

.tasks/2026-07-18-TSK-3-landing-redesign-TASKS.md

@@ -0,0 +1,30 @@
+# TSK-3 — Landing Redesign
+
+**Overall status:** DONE
+
+## TG-001 — Product and Design Context
+
+- **Owner:** Main agent
+- **Status:** DONE
+- **Acceptance:** `PRODUCT.md`, `DESIGN.md`, official benchmark, and critique define a truthful non-generic direction.
+- **Evidence:** Official Apple, Google, GitHub, Stripe, Cloudflare, and Linear surfaces were reviewed for hierarchy, proof, CTA, trust, and responsive patterns without copying trade dress. Impeccable v3.9.1 context, brand register, palette, and independent critique informed `PRODUCT.md` and `DESIGN.md`. Live mode is configured for the TanStack root document; no CSP was detected.
+
+## TG-002 — Product-Led Landing Surface
+
+- **Owner:** Main agent
+- **Dependencies:** TG-001
+- **Status:** DONE
+- **Acceptance:** Responsive page implements REQ-001 through REQ-007 without new UI dependencies.
+- **Evidence:** The product owner rejected the true-white/cobalt pass as generic. The replacement uses a distinctive redline identity, a custom contract-path mark, locally hosted Martian Grotesk, an immediate breaking-change painkiller, and a clearly labelled review prototype. Desktop and 390px mobile full-page screenshots have been inspected. No UI dependency was added.
+
+## TG-003 — Release Validation
+
+- **Owner:** Main agent
+- **Dependencies:** TG-002
+- **Status:** DONE
+- **Acceptance:** REQ-008 and REQ-009 validation, independent review, preview acceptance, and CI pass.
+- **Evidence:** The third visual direction is implemented. After product-owner review exposed an oversized desktop fold, the type scale, hero spacing, and downstream display sizes were tightened. The hero now uses the requested literal 7:5 copy-to-artifact grid with deliberate copy grouping and a stable single-column mobile fallback. Exact fold evidence at `.docs/TSK-3-fold-2048x1000.png` keeps the CTA and prototype visible without scrolling; full-page desktop and mobile evidence is also current. Accessibility, truthfulness, no-JavaScript, and narrow-screen checks pass. The product owner approved the updated preview on 2026-07-18; CI passes.
+
+## Ready Rule
+
+TG-003 and product-owner approval are complete. Merge is authorized by the approval; production remains separately gated.

DESIGN.md

@@ -0,0 +1,66 @@
+---
+name: OpenAPI Studio
+description: A decisive review surface for API contract changes.
+colors:
+  redline: '#cf2f1b'
+  ink: '#171310'
+  black: '#000000'
+  paper: '#f5f5f3'
+  white: '#ffffff'
+  muted: '#5e5853'
+  muted-light: '#aaa39d'
+  artifact-ink: '#e8e4dd'
+  artifact-muted: '#98918b'
+  artifact-rule: '#38332f'
+  rule: '#bcb7b0'
+  rule-light: '#cbc7c1'
+  impact: '#ff654b'
+  removed: '#ff8d7a'
+  removed-bg: '#39201d'
+  added: '#a4e1bc'
+  added-bg: '#173126'
+typography:
+  family: 'Martian Grotesk'
+  displayWeight: 680
+  displayStretch: '90%'
+  displayTracking: '-0.04em'
+  bodyLineHeight: 1.65
+rounded:
+  default: '0'
+---
+
+## Overview
+
+OpenAPI Studio is “precision under pressure”: an exacting contract-review instrument with the confidence of an editorial technology brand. Vermilion redline, black, white, and disciplined scale create recognition; the contract artifact supplies the substance. Never borrow another company’s trade dress.
+
+Physical scene: an API lead reviews a consequential contract diff on a bright office display, under time pressure, and needs the interface to feel exact rather than theatrical.
+
+## Color and Typography
+
+Redline is a committed brand field, not a small accent. Use ink and paper for long reading areas and impact coral only inside true breaking-change states. All pairings meet WCAG 2.2 AA. Martian Grotesk is locally hosted under OFL 1.1; use its width axis to make display type compact and assertive. Monospace belongs only inside contract artifacts.
+
+## Shape and Layout
+
+Stay structurally flat: square controls, hard rules, no ornamental radius, gradients, glass, or soft shadows. A single offset white plane may communicate the product artifact’s physical priority. Use a 90rem shell and asymmetric editorial grids. Each section gets a distinct narrative rhythm rather than repeated cards.
+
+### Composition Gates
+
+- Desktop H1 ceiling: `4.75rem`; mobile H1 ceiling: `4rem`; later display headings: `4.4rem` maximum.
+- The desktop hero uses a literal `7:5` copy-to-artifact grid and collapses to one column at `64rem`.
+- The 1440×900 and 2048×1000 folds must include the primary CTA, price condition, and complete review artifact without scrolling.
+- Header plus hero may not exceed the initial viewport height at supported desktop sizes.
+- Consequential copy—prototype status, pricing terms, privacy guidance, and artifact captions—never renders below `0.75rem`.
+- Full-page screenshots validate rhythm; viewport-only screenshots validate conversion. Both are required.
+
+## Components
+
+Navigation shares the hero field and has one dark pilot action. Product artifacts must show plausible OpenAPI paths, diffs, and review consequences and must be labelled when illustrative. Buttons are at least 44px high with visible focus. Numbering is reserved for the genuine three-step workflow.
+
+## Guardrails
+
+- Lead with the painkiller: catch a breaking change before users do.
+- Pair commercial claims with public source, delivery checks, or explicit boundaries.
+- Never fabricate customers, screenshots, certifications, metrics, or availability.
+- Avoid anonymous system-font minimalism, generic SaaS cards, decorative code, and fashionable effects.
+- Validate desktop, mobile, keyboard, reduced motion, no-JavaScript rendering, and 200% zoom.
+- Treat `.docs/design-reference-synthesis.md` as comparative guidance, not permission to copy another brand.

PRODUCT.md

@@ -0,0 +1,49 @@
+# Product
+
+## Register
+
+brand
+
+## Platform
+
+web
+
+## Users
+
+The primary audience is founders, backend leads, platform engineers, API designers, and developer-experience leads on software teams of roughly 2–30 engineers. They actively maintain OpenAPI 3.0 or 3.1 contracts and need to move a real change from editing through review and publishing without breaking meaning or losing trust.
+
+## Product Purpose
+
+OpenAPI Studio is being built as a dependable workspace for maintaining an API contract as shared product infrastructure rather than fragile YAML. The commercial objective is to move from $0 to the first $1,000 MRR by earning five design partners and validating repeated use, willingness to pay, and retention before expanding the feature surface.
+
+## Positioning
+
+OpenAPI Studio gives small API teams one clear, reviewable path from contract change to published truth without requiring a heavyweight API platform.
+
+## Conversion & proof
+
+- Primary CTA: review one costly contract change through a qualified founding-pilot conversation.
+- Secondary CTA: inspect the public source and delivery evidence on GitHub.
+- The line to remember: catch the breaking change before your users do.
+- Belief ladder: this is built for my team; it understands the real contract workflow; it is honest about what exists; its technical foundation is credible; the pilot is low-risk; $29 per workspace per month would be reasonable if it solves the repeated problem.
+- Proof on hand: a public repository, passing CI, a live Cloudflare preview, explicit OpenAPI 3.0/3.1 scope, privacy-bounded conversion telemetry, and transparent pilot terms. There are no customers, testimonials, production editor screenshots, or usage claims yet; none may be implied.
+
+## Brand Personality
+
+Exacting, assured, and accountable. The emotional goal is controlled urgency: a carefully engineered instrument for consequential work, not a timid enterprise template or a loud startup pitch.
+
+## Anti-references
+
+Do not resemble generic AI-generated SaaS, anonymous white/cobalt enterprise minimalism, warm editorial templates, terminal cosplay, abstract gradients, repeated card grids, glassmorphism, or unearned Apple imitation. Do not fabricate product UI or claim a workflow is available when it is only planned. Urgency must name a real contract consequence, never manufacture fear.
+
+## Design Principles
+
+1. Evidence before persuasion: every claim sits beside a truthful artifact, boundary, or verifiable delivery fact.
+2. One decision per fold: establish fit, show the workflow, resolve trust, then present the offer.
+3. Enterprise restraint, startup honesty: use disciplined hierarchy and finish without pretending to have customers, scale, or capabilities that do not exist.
+4. The contract is the visual subject: OpenAPI structure, changes, validation, and publishing provide the imagery—not generic decoration.
+5. Conversion without pressure: make the five-team pilot, response expectation, and $29 post-pilot price explicit.
+
+## Accessibility & Inclusion
+
+Meet WCAG 2.2 AA for the complete landing-page journey. Preserve semantic landmarks and heading order, keyboard operation, visible focus, 44px touch targets, 200% zoom usability, sufficient text and control contrast, readable line lengths, reduced-motion behavior, JavaScript-independent content and CTAs, and layouts without horizontal overflow.

public/fonts/MartianGrotesk-LICENSE.txt

@@ -0,0 +1,93 @@
+Copyright 2021 The Martian Grotesk Project Authors (https://github.com/evilmartians/grotesk)
+
+This Font Software is licensed under the SIL Open Font License, Version 1.1.
+This license is copied below, and is also available with a FAQ at:
+http://scripts.sil.org/OFL
+
+
+-----------------------------------------------------------
+SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
+-----------------------------------------------------------
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded, 
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.

specs/features/2026-07-18-landing-redesign/spec.md

@@ -0,0 +1,43 @@
+# Landing Redesign
+
+| Field           | Value                           |
+| --------------- | ------------------------------- |
+| Feature ID      | TSK-3                           |
+| Roadmap outcome | Phase 1 — Demand and Conversion |
+| Status          | SPEC_APPROVED                   |
+| Owner           | Product owner                   |
+| Updated         | 2026-07-18                      |
+
+## Problem and Outcome
+
+The current landing page is technically sound but visually generic, commercially unconvincing, and unsupported by product evidence. It must be replaced before outreach. The redesign must establish enterprise-grade trust without copying another company or implying that the unfinished editor already exists.
+
+## Requirements
+
+- **REQ-001:** Replace the rejected cream, moss, terracotta, mono-kicker, oversized compressed headline, numbered-card, and decorative-gradient system.
+- **REQ-002:** Lead with a precise OpenAPI contract outcome, intended team, honest pilot status, and one primary design-partner action.
+- **REQ-003:** Show a high-fidelity, clearly labelled sample contract-review artifact above the fold; it must not be presented as a currently available application screenshot.
+- **REQ-004:** Explain the proposed edit, review, and publish workflow using concrete OpenAPI structure rather than generic feature cards.
+- **REQ-005:** State current proof and boundaries: public source, passing delivery checks, OpenAPI 3.0/3.1 focus, no checkout, no fabricated customers, and no production editor access.
+- **REQ-006:** Present the founding offer as five design-partner places, a free pilot, and a transparent $29/workspace/month post-pilot hypothesis.
+- **REQ-007:** Preserve the qualified mailto flow, first-party identifier-free conversion events, JavaScript-independent CTA, and existing privacy constraints.
+- **REQ-008:** Meet WCAG 2.2 AA, keyboard, 200% zoom, reduced-motion, mobile, no-overflow, performance, and truthful-copy acceptance.
+- **REQ-009:** Use existing Solid, Tailwind, and platform capabilities; add no UI or animation dependency.
+
+## Non-Goals
+
+- Building the editor, authentication, checkout, scheduling, CRM storage, testimonials, customer logos, or production deployment.
+- Copying Apple, Google, GitHub, Stripe, Linear, or any other company’s trade dress.
+- Adding sections merely to make the page appear complete.
+
+## Validation
+
+- Content and evidence review confirms every availability, security, and workflow claim is true.
+- Desktop, 390px mobile, and 200% zoom screenshots receive explicit product-owner visual approval.
+- Playwright verifies CTA destinations, $29 copy, semantic structure, JavaScript-disabled usability, accessibility, and no horizontal overflow.
+- Impeccable critique and detector report no release-blocking design or technical findings.
+- `bun run check`, preview smoke testing, and GitHub CI pass before merge.
+
+## Approval Gate
+
+The product owner rejected the existing visual direction and authorized an autonomous Impeccable-led replacement benchmarked against enterprise product-marketing standards. Preview deployment, merge, outreach resumption, and production/custom-domain operations remain separately gated.