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.
Summary
Preserve benchmark evidence provenance from RuntimeEvent export through Harbor artifacts and fixed-prompt reporting.
The new token source field is optional so existing Harbor artifacts remain readable. Exact metering and
requireFinalUsageaccept only explicit final provenance; legacy events without source remain readable but provisional.Verification
node --test --test-concurrency=4 packages/core/dist/__tests__/runtime-event.test.js packages/headless/dist/__tests__/harbor-adapter.test.js packages/headless/dist/__tests__/cell-output.test.js packages/headless/dist/__tests__/harbor-cell.test.js packages/headless/dist/__tests__/harbor-task-runner.test.js packages/headless/dist/__tests__/fixed-prompt-controller.test.js packages/headless/dist/__tests__/harness-ab-report.test.js— 408 passed before the review follow-upnode --test --test-concurrency=3 packages/headless/dist/__tests__/cell-output.test.js packages/headless/dist/__tests__/fixed-prompt-controller.test.js packages/headless/dist/__tests__/harness-ab-report.test.js— 121 passed after the review follow-upnode --test --test-concurrency=3 packages/headless/dist/__tests__/provider-auth-proxy.test.js packages/headless/dist/__tests__/harbor-adapter.test.js packages/headless/dist/__tests__/harbor-task-runner.test.js packages/headless/dist/__tests__/pier-task-runner.test.js packages/headless/dist/__tests__/cell-output.test.js packages/headless/dist/__tests__/fixed-prompt-controller.test.js packages/headless/dist/__tests__/harness-ab-report.test.js— 364 passed, 1 environment-dependent skip after the final fresh-eye follow-upnpm --workspace @maka/headless run typechecknpx biome checkon all files changed by the review follow-upnpx biome formatandnpx biome linton the complete original TypeScript and JSON change setpython3 -m py_compile packages/headless/harbor/maka_trajectory.pyReview focus
This PR intentionally excludes Runtime terminal-ledger changes, error-content folding, QuickJS wiring, benchmark cohort machinery, and experiment-specific reporting.
Checklist
Does this PR entail a change in behavior?