Repository navigation
docs: Document cloud agent trace capture for PIG 0.3.5 and later - #1125
Merged
Merged
Conversation
…ive-trace-collection # Conflicts: # src/content/changelog/changelogs/september-2026.mdx
…ive-trace-collection # Conflicts: # src/content/changelog/changelogs/september-2026.mdx
…ive-trace-collection # Conflicts: # src/content/changelog/changelogs/september-2026.mdx
…ive-trace-collection # Conflicts: # src/content/changelog/changelogs/september-2026.mdx
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
3 tasks done
…agent-capture-5441 # Conflicts: # src/content/docs/docs/governance/get-started/enroll-your-hosts.mdx # src/content/docs/docs/governance/reference/supported-agents.mdx
3 tasks done
hawkeyexl
added a commit
that referenced
this pull request
Oct 19, 2026
…bularies (#1165) * Replace docmeta with manni and adopt strict manni metadata vocabularies Swap the deprecated docmeta CLI for @hawkeyexl/manni, validate docs frontmatter against the open and strict core, stewardship, audience, lifecycle, structure, and ai-context vocabularies, and fill their values on every docs page. Maintainer fields live in docs.metadata.yaml; created, last-updated, and owner are stamped from git and CODEOWNERS. * Re-derive last-updated stamps after merging main * Re-stamp last-updated for pages changed by #1103 and #1125 * Use the built-in TGDP schemas for page type and trim the custom schema to what manni doesn't cover Stack tgdp:templates:1.1 and tgdp:templates-strict:1.1 in manni.config.yaml, remove type (and the title/description requirements manni:core already enforces) from schemas/custom-frontmatter.schema.json, and move every docs page's type to a Good Docs Project template slug. * Drop the custom schema and TGDP strict overlay, and use manni's built-in Starlight schema Remove schemas/custom-frontmatter.schema.json (id requirement and tags check) and schemas/starlight-frontmatter.schema.json, replace the mirror with astro:starlight:0.41, drop tgdp:templates-strict:1.1, and update the manni workflow, AGENTS.md, and ADR 0005 to match. * Note that CI fails without a page id * Document manni check as the local verify step after meta derive `manni check` reports stale stamps but never restamps, so `meta derive` stays the fix. Pass page paths: a bare `manni check` exits 2 because its cite check can't match the ids in docs.metadata.yaml to pages (a manni bug). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: promptless[bot] <promptless[bot]@users.noreply.github.com> Co-authored-by: Manny Silva <hawkeyexl@gmail.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Open in Promptless
Coordination: #1047 (Cursor trace collection) has merged to
mainasa571437. This branch now includes that merge, so this PR can merge on its own.Proposed changes
Cloud agents such as Claude Tag run in sandboxes where no one can approve host enrollment in a browser. An organization admin creates a cloud integration grant on Settings → Cloud integrations. Each cloud execution then uses the grant to enroll itself and upload its native Claude Code or Codex traces to the customer's analyzer. Cloud enrollment first shipped in stable PIG 0.3.5 (schema revision 5) and works the same way in the current stable release, 0.3.6.
governance/get-started/capture-cloud-agent-traces.mdx. Covers:plicg_tokenPROMPTLESS_CLOUD_GRANTorPROMPTLESS_CLOUD_GRANT_FILE)pig cloud-bundlefor Claude Code, or running it directly for Codexplan-your-deployment.mdx,deploy-the-analyzer-worker.mdx,networking-and-identity.mdx, anddeploy-on-aws.mdx.pig-cli-reference.mdx. Addspig cloud-bundleand its options.enroll-your-hosts.mdxandsupported-agents.mdx. Point cloud sandboxes to the new page. docs: Document Cursor native trace collection for PIG (analyzer 0.3.3+) #1047's Cursor guidance is preserved.The
/pig/...dashboard route updates already landed in #1039, so this PR no longer carries them.Released capability compared with Claude Tag acceptance
Cloud enrollment is released: the routes, grants, dashboard page, and collector are on stable 0.3.5 and later, with no feature flag. Claude Tag has not completed a live end-to-end acceptance run. A Tag experiment showed that Tag adds
Authorizationwhen the collector leaves it out. It has not been confirmed that Tag passesX-Promptless-Producer-Tokenthrough to the analyzer. The page asks readers to confirm that before relying on Tag, which matches the dashboard's own notice. It makes no claim of a live Tag end-to-end success.Source evidence
schemaTo: 5, and their release notes say schema revision 5 is for cloud host enrollment.63e64e85, and 0.3.6 from625624a7. Both contain the cloud routes from Promptless/promptless#5441. 0.3.4 predates them./healthz,/v0/host-enrollment/policy,/v0/host-enrollment/check-ins,/v0/cloud-enrollment/leases, and/v0/traces/batches.625624a7.Authorization: Bearerheader. Theplicg_grant token is required on enrollment.X-Promptless-Producer-Token(plicl_) plus atargetquery parameter.934ae08.^[a-z][a-z0-9_]{0,63}$, lease 60–3,600 s, execution limit 1–100,000, expiry within 365 days.4c02abf.pig cloud-bundleoptions.--worker-urlmust be an HTTPS origin.cloud-capture.json, and the transport rules. Proxy mode fails if a grant variable is set.status.jsonstates, includingblockedwithbootstrap_upgrade_requiredwhen the host enrollment policy requires a newer collector.main.Checklist
Merge resolution:
f9152d9mergesmainata571437into this branch. The only conflicts were inenroll-your-hosts.mdxandsupported-agents.mdx. Both were resolved by keeping this branch's content, which already contained #1047's final head525383f.mainata571437has the same tree as525383f, so the resolved tree is the same as the reviewed753ce83. Onf9152d9,remark --frailand Vale report no findings on the eight changed files, anddocmeta validatepasses. Earlier validation on the combined head:npm run lint:md(remark--frail) anddocmeta validatepass. Vale (collection config plus Promptless and KB rules) reports no findings on any changed MDX file.npm run buildpasses. A local linkchecker crawl of the new page and its links found no broken links; the only errors were dev-server-only routes such as/sitemap-index.xmland/llms.txt. The external Claude Tag and pig-deploy links return 200, and the#restrict-by-path-or-methodanchor exists.Trigger Events