docs(agents): broaden supabase-backend-auditor triggers to api/* (THI-339)#368
Merged
Merged
Conversation
…ad/storage/secret routes (THI-339) Self-critique finding from the 02/06 WS3 re-run (first run post-THI-326): the Resend sender lives in a Vercel Edge route (api/support/notify.ts), not a Deno Edge Function. The frontmatter only listed supabase/functions/* as a trigger, so the agent could be skipped on the very file it should audit (backend secret + BOLA on an object). Broaden the trigger: the discriminant is the SURFACE (upload / storage / secret-backend), not the runtime (Deno vs Vercel Edge). Single-line frontmatter edit, no colon+space (THI-326 trap), guarded by src/test/agentFrontmatter.test.ts (21/21 green). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Sorry @thierryvm, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
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.
Contexte
Finding d'auto-critique de scope remonté par
supabase-backend-auditorlui-même lors du re-run WS3 du 02/06/2026 (son tout premier run post-fix THI-326, enfin invocable).En auditant la surface support (THI-319/320/325), l'agent a localisé le sender Resend dans une route Vercel Edge
api/support/notify.ts— pas dans une Edge Function Denosupabase/functions/*.Gap corrigé
Le
description:frontmatter listait comme triggerssupabase/functions/*, policystorage.objects, code d'upload, et rendu de contenu uploadé — mais pas les routesapi/*Vercel qui manipulent un secret backend (RESEND_API_KEY) ou font du BOLA sur un objet. Le body (ligne 10) couvrait déjà la frontière de scope surapi/support/notify.ts, mais le trigger ne la captait pas → un main agent lisant la description au pied de la lettre pouvait ne pas invoquer l'agent sur le fichier qu'il devait justement auditer.Le bon discriminant = la SURFACE (upload / storage / secret-backend), pas le RUNTIME (Deno vs Vercel Edge).
Changement
1 ligne de frontmatter : ajout d'une phrase au
description:élargissant le trigger aux routesapi/*runtime-agnostic.Sécurité du changement (anti-THI-326)
:(colon+espace) réintroduit dans la valeur YAML (le piège exact qui empêchait l'agent de se charger avant fix(agents): repair YAML frontmatter so 2 security auditors register (THI-326) #365).src/test/agentFrontmatter.test.ts→ 21/21 green en local..claude/agents/*.mdn'est pas dans le bundle Vercel → zéro impact runtime prod.Liens
🤖 Generated with Claude Code