Include iteration artifact evidence

[s-hiraoku]

Summary

• include per-iteration changedFiles and discoveredIssues in the iteration artifact contract
• write changed-files.json and discovered-issues.json under each iteration directory
• update CLI artifact regression coverage, README, and committed dist output

Verification

• npm test
• npm run validate:json

Closes #58

[coderabbitai]

Warning

Review limit reached

@s-hiraoku, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 27 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository: kaizen-agents-org/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 5aadce6d-87b4-48c1-bd7f-d93bc6a2c7da

📥 Commits

Reviewing files that changed from the base of the PR and between f2abdc1 and a94a428.

⛔ Files ignored due to path filters (5)

• dist/artifacts.d.ts.map is excluded by !**/dist/**, !**/*.map
• dist/artifacts.js is excluded by !**/dist/**
• dist/builder/BuilderAgent.js is excluded by !**/dist/**
• dist/types/contracts.d.ts is excluded by !**/dist/**
• dist/types/contracts.d.ts.map is excluded by !**/dist/**, !**/*.map

📒 Files selected for processing (5)

• README.md
• src/artifacts.ts
• src/builder/BuilderAgent.ts
• src/types/contracts.ts
• test/builder-agent.test.js

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/iteration-artifact-evidence

---

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.}

[s-hiraoku]

Guardian check complete.

• CI: passing (test)
• CodeRabbit: status success; no actionable review threads were created (review limit notice only)
• Merge state: CLEAN
• Closing linkage: Closes #58 is recognized by GitHub

[s-hiraoku]

Guardian check complete.

• Final state: CLEAN / MERGEABLE
• CI watched: GitHub Actions test passed after push a94a428
• CodeRabbit: status success; no actionable review threads present
• Fixes pushed: merged current origin/main to resolve the DIRTY merge state; regenerated build outputs and resolved dist/types/contracts.d.ts.map
• Local verification: npm test and npm run validate:json
• Review threads: 0 unresolved
• Closing linkage: Closes #58 is recognized by GitHub

[s-hiraoku]

PR Guardian follow-up: this PR branch is now fully contained in main (ahead_by=0), with no remaining review threads and the prior test/CodeRabbit checks passing. There is no remaining diff to merge, so I am closing this redundant PR rather than leaving it in a non-mergeable empty state.