[corylanou]

Summary

Add a Gopher Guides article showing how Hype reads real Go source and captures command output during a documentation build. The walkthrough changes working code, demonstrates execution failures, and separates structural validation, execution validation, and export.

Include a runnable example, live build-time tags, tested commands pinned to a Hype revision, and links to the related documentation workflows. Explain where prose review and behavioral tests are still needed.

Closes #19

Type

• Content (new article or content update)
• Layout/Theme (template or styling changes)
• Infrastructure (Dockerfile, CI, config)
• Other

Test Plan

• make build succeeds: 19 articles, no warnings; new article renders with real code and output
• make dev shows changes correctly in browser
• No broken internal links or missing assets
• Copy-paste test installation, clone/setup, validation, and Markdown/HTML export commands against Hype revision 79c0476cad27
• Verify source and output update after changing the greeting; help updates after changing the flag description
• Verify broken Go code passes structural validation but fails execution validation and export
• Go build, vet, lint, and vulnerability checks; runnable example uses only the standard library
• Cory voice reference comparison, independent opening cold read, and closing no-ai-slop pass

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.