Repository navigation
feat: enable consented agent actions and canonical discovery - #449
Merged
Merged
Conversation
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
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.
External assistants could discover HitKeep analytics but could not use existing product operations with explicitly delegated authority. This adds API-resource OAuth scopes to the existing REST owners, team-only billing consent, optional synchronous aggregate A2A analytics, browser action confirmation, and canonical product-skill discovery and archives.
New agent surfaces require
AIEnabled. Delegated requests intersect the grant resource, exact scope, consented team/sites, revocation state and current permissions. Browser mutations require human confirmation and pin the approved team. ACP/UCP reuse Stripe Checkout and require a billing administrator's human payment approval. Production MCP stays read-only and aggregate-only; credentials and raw exports retain their human-only flows. Native MPP/x402/AP2 settlement and Web Bot Auth remain unavailable.Independent Ponytail and code reviews passed on
41d5c3e6e42636537d3cc3c85ad36a28d81745b0after fixing the retention team lookup, dated ACP request shape, prefixed browser schema URLs and an inherited checkout/webhook state race. Regression tests reproduced the failures before the fixes.Validation: all 26 canonical
prstable gates passed in GitHub CI on the exact reviewed Git tree6a7ad699e4b21f6e6a18ef16170f378b26a1867f, with zero coverage gaps. CI 41461726316 attempt 2, release validation, govulncheck, and workflow security succeeded. The first lint attempt failed on a Go module proxy HTTP/2 download error; retry passed without source changes. Duplicate local PR run20261102T142720-cf9ccd36is superseded by this complete CI evidence; it is not reported as passed. Final hygiene20261102T142524-89650093passed. Selectedfullcloud run20261102T142822-486f0c20independently passedcloud-build,cloud-testandcloud-image.The canonical stable Release pipeline separately enforces supported-floor Docker/Compose/Helm upgrade evidence using the tracked immutable fixture. That release certification remains required before production publication.
Companions are merged: assistant skills #6, docs #28, and infrastructure #15. The producer pin
4f2c2f8d4bc917629bbfaf61748c6636b04c88d1is preserved in assistant main. The docs OpenAPI mirror matches the reviewed app export after example-origin normalization (291 paths, 341 operations). Infra is applied in US/EU with final zero-change previews. The app's release docs-validation pin targets reviewed docs main6f5ea8961532400f776d19d9098f7a57f00434a7.Production app release, Cloud rollout and final live verification follow separately through repository workflows. No real payment or live assistant-client certification is claimed.