Repository navigation
Conversation
Feature pages stated no price, retention or setup doc, and their .md twins dropped the extra sections, so an agent reading /features/kubernetes-monitoring.md never saw the Helm install. - A plan block on every feature page and its .md twin: plan and meter rates from the same getOffer() as /pricing, retention per signal, the Superwall scale claim and the setup doc. - The .md twins render each page's extra sections (install commands, product event snippets, status page feeds) from data now shared with the components. - The roadmap lists what has shipped (Agent Sessions, self-hosting, uptime, status pages, SLOs, on-call, EU region, and more) instead of showing AI observability as in progress. - The MCP page lists Cursor, the tool count and every kind of write; llms.txt counts the feature pages from the registry. - getOffer() makes one Autumn request per build instead of one per render. - ja/ko gain the missing pricing_rate_included string.
…, uptime and MCP wording
This comment has been minimized.
This comment has been minimized.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 14 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
Maple review🟢 Confidence 10/10 · safe to merge. The only delta since the reviewed commit is a two-line type fix in one Astro file, and it type-checks the icon lookup without changing what renders. The delta since the last review is a two-line change in
|
Feature pages never said what a feature costs, how long it keeps data, or where its setup doc lives. Their
.mdversions also dropped the extra sections, so an agent reading/features/kubernetes-monitoring.mdnever saw the Helm install that the HTML page shows. The roadmap still listed AI observability as in progress, months after Agent Sessions shipped.What changed
A plan block on all 14 feature pages (HTML and
.md):getOffer()as/pricing;/docs/reference/retention;It comes from
lib/feature-plan.ts, so the page and its.mdversion can't disagree. Code review bills under AI usage. Alerts, status pages and MCP have no meter of their own and say so..mdversions include the extra sections. Snippet data moved tolib/feature-sections.ts, and the section components and the.mdversions both read it. Covered: the k8s install, product event snippets, status page feeds, uptime check traces, and CI and after-merge review.Roadmap catches up. Newly marked shipped: Agent Sessions, self-hosting, the service API view, investigations, the EU region, product events, code review, uptime, anomaly detection, status pages, SLOs and on-call. Dates come from the changelog and git history. Continuous profiling is in progress.
MCP page facts list Cursor, 130+ tools and every kind of write. The documented write tools cover on-call, SLOs, uptime, status pages, dashboards and ingest rules.
llms.txtcounts the feature pages from the registry instead of hard-coding 8 names.getOffer()makes one Autumn request per build instead of one per page render. The site is fully static, so the cache never outlives a build.ja/ko gain
pricing_rate_included, which the pricing page was already rendering in English.Verification
bun run testinapps/landing: 25 files, 198 tests pass. The newfeature-markdown.test.tschecks:.mdversion states the plan and the scale proof;.mdquotes the per-GB rate, the retention and the docs link;helm upgrade --installcommand;llms.txtcounts the registry.bun run buildsucceeds (315 pages). I checked the builtdist/features/*.mdby hand.autumn.config.ts, the changelog and git history. Its fixes are in the second commit.Screenshots
Log management, desktop:
Mobile (390px):
Japanese:
Roadmap after the catch-up:
The roadmap has nothing under Next or Later now, and its own empty state ("Nothing here yet") renders there. Real planned items need a product decision, so I didn't invent any.
🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.