Add a public-data readiness pilot interest page

Start by locating the static Quarto site entry points and existing build and assertion conventions; then review how public GitHub Issue Forms are defined. Run the Quarto render and public-boundary assertions, and check desktop and mobile screenshots to confirm the pilot page and closed-choice form meet the stated safety and readability criteria.

Goal

Add a public, no-payment page for teams to register non-binding interest in a Korean public-data API readiness pilot.

Scope

• Add one clearly labelled pilot page to the static Quarto site.
• Add a public GitHub Issue Form with closed choices for integration stage, problem category, desired output, installation or trial interest, and non-binding budget range.
• Add concise safety copy that rejects API keys, endpoint URLs, payloads, company names, contact details, and other private information.

Acceptance criteria

• The page explains that this is an interest test, not a service order, paid offer, SLA, or support channel.
• The page links to the Issue Form and does not use a form backend, analytics change, or email address as an unverified inbound path.
• The Issue Form requires no free text and states that all submissions are public.
• Existing site build succeeds and the new page is readable at desktop and mobile widths.

Out of scope

• Any payment collection, customer support, Datapan runtime/API change, domain/DNS change, analytics change, or portfolio-home rewrite.

Evidence

• Quarto render succeeds.
• Static form and public-boundary assertions pass.
• Desktop and mobile screenshots demonstrate readable hierarchy and controls.