Repository navigation
docs: audit four more guides against the code - #124
Merged
Merged
Conversation
Checked on 2026-10-02; tutorial 14 run again, approve and reject paths. - Connect an agent: response table rewritten from the server (200 means executed; 429, 502, 503 and 500 codes; timeout advice from G-84); a missing connector is 503, not an approved 500; the repo copy docs/connectors/CONNECTING_AN_AGENT.md becomes a pointer, so there is one copy. - Live API and demos: production has no demo key (keys rebuilt 2026-09-27 and 2026-09-30); executed actions do have Trust Records; scoped key example instead of "*". - Write your first policy: the documented reject recipe no longer rejected (the tutorial always attaches the approval); replaced with vendorVerified false, run and quoted. - Deploy patterns: PARMANA_STORAGE=postgres works (same implementation as supabase, G-57) instead of throwing; DATABASE_URL and migrations; agent keys need allowed capabilities; Vercel redeploy for key changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully deployed
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.
What
Page by page audit, batch 7: four guides integrators use most, checked against the code on 2026-10-02.
Real errors fixed:
200means authorized with dispatch after, and that a missing connector is an approved500. A200is returned only after the action ran and its Trust Record was signed; a missing connector is503 CONNECTOR_NOT_REGISTERED. Table rewritten with429,502,503,500 EXECUTION_RECORD_INCOMPLETEand the G-84 timeout advice. The repo copydocs/connectors/CONNECTING_AN_AGENT.mdhad drifted with the same errors; it is now a pointer to this page (references to it still resolve).demokey with"*"; production keys were rebuilt on 2026-09-27 and 2026-09-30 and there is no demo key (the sandbox has one). Said no Trust Record can be fetched; executed Paytm refunds have one. Key example now scoped, not"*".financeDirectorApproved: false) no longer rejects, because the tutorial attaches the director's approval. Replaced withvendorVerified: false, run and quoted.PARMANA_STORAGE=postgresthrows; it uses the same implementation assupabase(G-57). AddedDATABASE_URLand migrations, scoped agent keys, Vercel redeploy for key changes.Not verified: which connector credentials production has today (the Vercel token here cannot read the project); the live API page states it as of the operator's 2026-09-30 check and says how to confirm.
🤖 Generated with Claude Code