Conversation
…eting review) Head-of-marketing critique of the README, all actionable items applied: - Quick-links row under the banner (evo/drizzle/posthog pattern), including "Why whittle?" as a nav link to docs/why-write-time.md — the posthog form of a Why section, surfacing the argument without top-of-page marketing prose. - Hero leads with the fidelity promise; routing demoted to the optional clause (one crisp promise for the 3-second read; routing is the second surface). - Highlights 7 -> 5 (fail-open+local merged, executable-claims folded into the motif line); fail-open deduped from 5 mentions to 2 load-bearing ones. - Comparison table in "Why write-time?" — the differentiating axes vs read-time proxies, evidence-shaped instead of adjective-shaped. - Who-this-is-for line, honest star ask, explicit near-term roadmap, real alt text on the banner. - Dev version baseline bumped to 0.3.0 ahead of the tagged release that ships the router (the release itself resolves the README-vs-@latest gap the review flagged as P0). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Verified post-release: `go install ...@latest` correctly fetched v0.3.0, but the binary printed the baseline var (plain go install runs no ldflags). Prefer the module version from runtime/debug.ReadBuildInfo when goreleaser didn't inject one, so @latest users see the tag they actually installed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Applies the head-of-marketing critique: quick-links row under the banner (evo/drizzle/posthog pattern) with Why whittle? as a nav link to the write-time argument, hero leads with the fidelity promise, Highlights 7→5, fail-open deduped to two load-bearing mentions, a differentiating-axes comparison table in Why write-time, who-this-is-for line, honest star ask, explicit roadmap, real banner alt text. Dev version baseline bumped to 0.3.0 for the release.
🤖 Generated with Claude Code