docs: link out to the hosted tools from the six pages that earn it - #6
Merged
Conversation
This branch already carried the curated 0.2.0 release. It has drifted behind the development tree since, and this is that delta — eighteen files, no deletions, no new files. Most of it is the cross-linking to the hosted tools. Six documentation pages now link out at the point where the reader has the question the tool answers: lifecycle and quickstart to the inspector, policy and cli to the policy playground, errors to replay, recipient-rotation to history. public/llms.txt gains an entry so an agent reading the index can discover them at all. reference/errors.mdx is generated, so its link lives in tools/docs-gen/index.js rather than in the page. Adding it to the page by hand is what made docs:check fail on the development repository: the generator would have silently deleted the link on the next run, and in the meantime the staleness check failed three CI jobs. The page here is the regenerated output and matches. The rest is ordinary drift the same build carries across: the release workflow, the markdown-mirror script, the stylesheet, and prose fixes to migration, durable-object, gateway, cli, AGENTS.md, SECURITY.md and the examples README. .github/workflows/docs.yml is deliberately still absent. Rebuilding the public tree from the development repository does not restore it, and it should not: 1d06900 removed it because it deployed the site exactly never — one cancelled run — while Cloudflare Pages' Git integration has served docs.tx402.io all along, and a second deploy path onto the same project would race the first. Docs deploy with pnpm docs:deploy. This was worth stating because a wholesale tree replacement is exactly the operation that would quietly put it back. Verified: build-public-tree.sh reports 472 tracked, 43 dropped, 429 shipped with every exclusion assertion passing; pnpm --filter tx402 build; pnpm docs:check reporting both generated pages current.
jaykomarraju
changed the title
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.
Adds the outbound links to the hosted tools at tools.tx402.io. 42 lines across 8 files, nothing else — verified with
git diff --stat origin/main release/0.2.0.guides/lifecycle/inspectguides/policy/policyreference/errors/replaystart/quickstart/inspectguides/cli/policyoperations/recipient-rotation/historyPlus a
tools.tx402.ioentry inpublic/llms.txt, without which an agent reading the index cannot discover the tools at all.Anchor text is the question the reader has at that point, not the product name. Nothing in the copy characterizes an endpoint or its operator.
reference/errors.mdxis generatedIts link lives in
tools/docs-gen/index.js, not in the page. Adding it to the page by hand is what failed three CI jobs on the development repo —docs:checkcaught it as stale, and the nextdocs:generatewould have deleted the link silently. The page here is the regenerated output.Correcting this PR''s original description
I opened this as
release: 0.2.0, claiming this repository was on 0.1.0 and that the release had never been pushed. That was wrong.mainhas been 0.2.0 since its own PR #1, with four PRs of fixes on top. My local clone was 8 commits behind and I diagnosed from it without fetching, so a stale working tree got reported as the state of the remote.The branch is 7 commits behind
mainfor the same reason. It is still safe to merge — the tree diff againstorigin/mainis only the 42 lines above, because the development tree already contained those four PRs of fixes — but it should be read as a docs change, not a release.Verified:
pnpm --filter tx402 build,pnpm docs:checkreporting both generated pages current.