DOC-6955 Repoint the Google ADK links at Agent Memory's new home - #3785
Merged
Conversation
Ten relref calls across three Google ADK pages still named Agent Memory paths that
moved to operate/iris. Repointed to the new locations, confirmed with Andy as the right
targets rather than assumed, since both pages moved across product areas and a link's
intended destination is not always the file's new home.
/develop/ai/context-engine/agent-memory/self-managed -> /operate/iris/agent-memory/self-managed (7)
/operate/rc/context-engine/agent-memory/create-service -> /operate/iris/agent-memory/create-service (3)
The reader-facing damage was worse than the ticket recorded, and only visible on the
rendered page. Both old URLs return 200, because the moved pages carry aliases for them,
so it looked as though readers were being redirected and only the build was complaining.
They were not: relref resolves pages, not aliases, so a relref naming an alias path fails
even while that URL works. With refLinksErrorLevel set to WARNING the failure is not
fatal, and Hugo emits an empty string -- so the live pages render three `<a href="">`
anchors that go nowhere. Typing the old URL worked; clicking the link did not.
Verified against a build rather than by reading the diff. Before: three empty hrefs on
the live ADK index. After: zero empty hrefs across all three pages, ten resolved links
to the new targets, and no REF_NOT_FOUND anywhere in the build. The six sibling refs to
`/develop/ai/context-engine/agent-memory`, its `api-reference` and
`/operate/rc/context-engine/agent-memory` are deliberately untouched -- those paths still
have real pages, restored as bridges during the restructure, which is why only two of the
five targets broke.
Worth noting for the next time this happens: DOC-6951's scanner could not have caught
this. It reads git rename records and reasons about URLs, and relref targets are resolved
at build time from content paths, so broken inbound references are invisible to it. The
signal that exists today is a build warning nobody reads.
Learned: both dead URLs returned 200 because aliases covered them, which made this look like a build-only complaint -- the rendered page was the only place the empty hrefs showed, so severity had to be read off the HTML rather than the status codes
Constraint: relref resolves pages and not aliases, so a relref naming an alias path fails at build time even though that URL serves a redirect
Ticket: DOC-6955
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Contributor
🧠 Redis MemoryFound 5 related items from repository history (5 new this commit):
Memory updated at e542e89 |
Contributor
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
2 participants
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.
Note: the AI description below is longwinded but the basic idea is that these links were pointing to the old locations of the files and so they were only being resolved by aliases. This PR fixes the links so they point directly to the appropriate pages.
Fixes DOC-6955. Ten
relrefcalls across three Google ADK pages named Agent Memory paths that moved tooperate/iris./develop/ai/context-engine/agent-memory/self-managed/operate/iris/agent-memory/self-managed/operate/rc/context-engine/agent-memory/create-service/operate/iris/agent-memory/create-serviceTargets confirmed rather than assumed — both pages moved across product areas, so the file's new home isn't automatically the link's intended destination.
The damage was worse than the ticket recorded
Both old URLs return 200, because the moved pages carry aliases for them. That made this look like a build-only complaint with readers being redirected safely. They weren't.
relrefresolves pages, not aliases, so a relref naming an alias path fails at build time even though the URL itself serves a redirect. WithrefLinksErrorLevel = "WARNING"that failure isn't fatal and Hugo emits an empty string — so the live pages render<a href="">: anchors that go nowhere. Typing the old URL worked; clicking the link did not.That severity was only visible in the rendered HTML. Status codes said everything was fine.
Verified against a build, not the diff
href=""on the ADK indexREF_NOT_FOUNDin the buildThe six sibling refs to
/develop/ai/context-engine/agent-memory, itsapi-reference, and/operate/rc/context-engine/agent-memoryare deliberately untouched — those paths still have real pages, restored as bridges during the restructure, which is why only two of the five referenced targets broke.Note for next time
DOC-6951's scanner could not have caught this. It reads git rename records and reasons about URLs;
relreftargets resolve at build time from content paths, so broken inbound references are invisible to it. The only signal today is a build warning nobody reads — worth considering whetherrefLinksErrorLevelshould beERRORfor new breakage, though that would fail the build on any pre-existing instance.🤖 Generated with Claude Code
Note
Low Risk
Documentation-only link target updates with no application or infrastructure code changes.
Overview
Updates 10 Hugo
relreftargets across the Google ADK integration docs (_index.md,redis-agent-memory.md,agent-memory-server.md) so provisioning and self-managed setup links follow Agent Memory’s new location under/operate/iris/agent-memory/.Self-managed links move from
/develop/ai/context-engine/agent-memory/self-managedto/operate/iris/agent-memory/self-managed(7 occurrences). Create service links move from/operate/rc/context-engine/agent-memory/create-serviceto/operate/iris/agent-memory/create-service(3 occurrences). Other Agent Memory refs (overview, API reference, RC overview) are unchanged.This fixes broken in-page links: stale paths may still redirect in the browser, but
relrefresolves content paths only, so the old targets produced emptyhref=""anchors at build time.Reviewed by Cursor Bugbot for commit e542e89. Bugbot is set up for automated code reviews on this repo. Configure here.