Repository navigation
fix(edge): serve synced marketing sitemap, list /blog/ surface - #102
Merged
Merged
Conversation
/sitemap.xml was generated from a hardcoded six-route catalog, so the synced marketing sitemap (with all /blog/ articles) was never served. Pass env into the agent edge and prefer ASSETS for /sitemap.xml, keeping the generated catalog as the no-bindings fallback used by tests. Also registers the stable /blog/ index in the agent catalog and llms.txt so /api/ai and the discovery surfaces stay truthful. Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.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.
Summary
/sitemap.xmlwas generated inagent-edge.mjsfrom a hardcoded six-route catalog — the syncedmarketing/sitemap.xml(14 URLs incl. all 7 blog articles) never reached production even though blog pages serve.handleAgentEdge(request, env)now prefersenv.ASSETSfor/sitemap.xml→ the synced file serves and stays correct on every future marketing sync. Falls back to the generated catalog when bindings are absent (tests)./blog/index toAGENT_SURFACE.catalog.surfaces(now 7) and the llms.txt Product list so/api/aiand discovery surfaces stay truthful.Test plan
vitest src/agent-edge.test.ts src/worker.test.ts— 14/14tsc --noEmitclean; biome format applied/sitemap.xmllists/blog/URLs after deploypnpm checkfails at pristine HEAD on a whitespace hook over tracked.fleet//.impeccable/files — pre-existing, unrelated.Generated with Devin