feat(agent): add decision snapshot provenance#363
Open
bitloi wants to merge 2 commits into
Open
Conversation
JSONbored
requested changes
Jun 5, 2026
Owner
JSONbored
left a comment
There was a problem hiding this comment.
@bitloi the provenance direction is useful, but the migration sequencing blocks this branch.
A few notes:
- Adding public-safe provenance plus authenticated-only fields is aligned with #282.
- The new migration reuses
0020, and other open PRs also introduce0020migrations. - That cannot land safely because whichever PR merges first will make the others stale or ambiguous.
Required changes:
- Rebase onto current main and allocate the next available migration number.
- Confirm the generated OpenAPI artifact matches the final schema.
- Recheck that public serialization only includes public-safe provenance.
Validation expected:
- Rerun migration-related tests, agent-orchestrator/provenance tests,
npm run ui:openapi:check, andnpm run typecheck.
726036f to
85a633b
Compare
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.
Summary
agent_context_snapshotsthrough a nullableprovenance_jsoncolumn and exposed it in theAgentContextSnapshotOpenAPI schema.provenance.publicSafe.Scope
CONTRIBUTING.mdand does not reintroduce GitHub Pages, VitePress,site/, orCNAME.Validation
git diff --checknpm run actionlintnpm run typechecknpm run test:coveragelocally; global coverage stays at or above 97% for lines, statements, functions, and branches (aim for 98%+ branch coverage locally so CI variance does not fail near the threshold)npm run test:workersnpm run build:mcpnpm run test:mcp-packnpm run ui:openapi:checknpm run ui:lintnpm run ui:typechecknpm run ui:buildnpm audit --audit-level=moderateIf any required check was skipped, explain why:
npm run test:cipassed locally and covers the required gate. A sandboxednpm run test:coverageattempt failed because local fixture servers cannot bind127.0.0.1in the sandbox; the unsandboxed required gate passed.Safety
AgentContextSnapshotOpenAPI schema and the generated UI OpenAPI artifact were updated.Notes
provenance_jsonis nullable and parsed asnullwhen absent.