feat(eval): add ai-tools-roundup-2026 deterministic fixture bundle

[BrianCLong]

Motivation

• Capture the ITEM (public social roundup) as a Summit-owned, machine-verifiable fixture so it can be treated as a market-signal rather than a product spec.
• Provide a Minimal Winning Slice (MWS) baseline that produces deterministic, evidence-backed artifacts for the Intel-to-Brief flow.
• Enable CI-gated determinism and schema validation before adding evaluators, adapters, or execution handoffs.

Description

• Add an additive subsumption fixture lane under .artifacts/subsumption/ai-tools-roundup-2026/ including fixtures/item-manifest.json, fixtures/public-url-fixtures.json, and fixtures/transcript-fixture.md for deterministic inputs.
• Seed deterministic output artifacts report.json, metrics.json, stamp.json, brief.md, deck-outline.json, qa-pack.json, and handoff-manifest.json with stable evidence IDs and dry-run handoff defaults.
• Introduce JSON Schema contracts for report.schema.json, metrics.schema.json, and stamp.schema.json enforcing evidence patterns and stable stamp keys.
• Add __tests__/subsumption/report-determinism.test.ts to assert byte-stability for report.json/metrics.json and deterministic stamp.json keys.

Testing

• Ran the new determinism test with node --import tsx --test __tests__/subsumption/report-determinism.test.ts, and the test suite passed.
• An initial attempt with node --test __tests__/subsumption/report-determinism.test.ts failed due to Node ESM handling of .ts files, after which the --import tsx runner was used successfully.
• Committed changes in an isolated additive commit (feat(eval): add ai-tools-roundup deterministic fixture pack, commit 3258001a98) and verified the new test passes in the workspace.

{"agent_id":"antigravity","confidence":0.90,"change_class":"feat(eval):fixture","commit":"3258001a98","rollback":"revert commit 3258001a98"}

---

Codex Task

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Warning

Rate limit exceeded

@BrianCLong has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 14 minutes and 9 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 14 minutes and 9 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1466cc41-4053-4100-b27d-f4f884ceae8d

📥 Commits

Reviewing files that changed from the base of the PR and between d6b3633 and 15ab0e3.

📒 Files selected for processing (14)

• .artifacts/subsumption/ai-tools-roundup-2026/brief.md
• .artifacts/subsumption/ai-tools-roundup-2026/deck-outline.json
• .artifacts/subsumption/ai-tools-roundup-2026/fixtures/item-manifest.json
• .artifacts/subsumption/ai-tools-roundup-2026/fixtures/public-url-fixtures.json
• .artifacts/subsumption/ai-tools-roundup-2026/fixtures/transcript-fixture.md
• .artifacts/subsumption/ai-tools-roundup-2026/handoff-manifest.json
• .artifacts/subsumption/ai-tools-roundup-2026/metrics.json
• .artifacts/subsumption/ai-tools-roundup-2026/qa-pack.json
• .artifacts/subsumption/ai-tools-roundup-2026/report.json
• .artifacts/subsumption/ai-tools-roundup-2026/schema/metrics.schema.json
• .artifacts/subsumption/ai-tools-roundup-2026/schema/report.schema.json
• .artifacts/subsumption/ai-tools-roundup-2026/schema/stamp.schema.json
• .artifacts/subsumption/ai-tools-roundup-2026/stamp.json
• __tests__/subsumption/report-determinism.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/add-intel-to-brief-workflow-for-ai-tools

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 15ab0e3d38

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Run determinism check against two generated outputs

This test currently compares runA and runB after loading the same committed report.json/metrics.json files, so it never exercises the artifact-generation path and cannot detect runtime nondeterminism (for example, unstable ordering or seed-dependent output in the producer). In CI this can produce a false green signal for determinism even when actual fixture generation is non-reproducible.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Store full SHA-256 digest in fixture stamp

The fixture_hash value is labeled as sha256: but only contains 40 hex characters, which is SHA-1-length rather than SHA-256-length. Any downstream verifier that expects a valid SHA-256 digest will reject or mis-handle this stamp, undermining the "machine-verifiable" integrity contract for the fixture bundle.

Useful? React with 👍 / 👎.