kaizen: 実行済み smoke artifact を docs/smoke-runs に永続化しました。 (#131)

[s-hiraoku]

Closes #131

Summary

実行済み smoke artifact を docs/smoke-runs に永続化しました。
issue #157 / PR #164 / verifier open_pr / closingIssuesReferences / guardian success を記録しています。
docs/13-sandbox-smoke.md にリポジトリ内保存先を追記しました。

Builder notes

制約に従い gh・push・PR 作成は実行していません。検証: npm test, npm run typecheck, npm run build, skill file checks passed.

Provider evidence:

• codex: exitCode=0, status=selected, failureClass=none, fallbackReason=none, payloadSource=last-message
  Selected backend: codex
  Final payload source: last-message

Verification

• npm test
• npm run typecheck
• npm run build
• test -f skills/gh-link-issue-pr/SKILL.md && test -f skills/kaizen-bug-router/SKILL.md && test -f skills/pr-guardian/SKILL.md

Verifier

verifier: open_pr
summary: Open PR with 0 should_fix item(s); risk is low.
notes: risk=low
confidence=82

Kaizen risk policy

Verifier cleared PR: Open PR with 0 should_fix item(s); risk is low.

Changed files: 2
Changed lines: 77

Summary by CodeRabbit

• Documentation
  • Clarified where to store smoke-run readiness evidence so it can be preserved outside a local machine.
  • Added a saved smoke-run report to the project docs for easier review and traceability.

[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: 55 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: 9362f7f7-e7e7-42a3-9eef-51d98b68904f

📥 Commits

Reviewing files that changed from the base of the PR and between fc6c0b4 and 87dbb2a.

📒 Files selected for processing (1)

• docs/smoke-runs/2026-07-04T07-49-09Z-issue-157.json

📝 Walkthrough

Walkthrough

This PR updates sandbox smoke documentation to instruct copying durable smoke-run readiness evidence into a repository-accessible path, and adds a new JSON artifact recording a completed sandbox smoke run for issue #157.

Changes

Sandbox smoke evidence

Layer / File(s)	Summary
Artifact location instructions and recorded smoke-run evidence docs/13-sandbox-smoke.md, docs/smoke-runs/2026-07-04T07-49-09Z-issue-157.json	Documentation now instructs copying smoke-run readiness JSON into docs/smoke-runs/<run-id>-issue-<number>.json, and a new artifact JSON records a completed sandbox smoke run's metadata, verification steps, PR details, and guardian outcome for issue #157.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related issues

• [sandbox-smoke] Verify Kaizen issue-to-PR path 2026-07-04T07:49:04.852Z #157: The new smoke-run artifact directly records evidence for the sandbox smoke issue-to-PR flow described in this issue.

Possibly related PRs

• kaizen-agents-org/kaizen-loop#100: Extends the sandbox smoke documentation/artifact workflow this PR builds upon.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes persisting the smoke artifact into docs/smoke-runs and references the linked issue.
Linked Issues check	✅ Passed	The PR adds a durable repo-local smoke artifact with the required issue, PR, verifier, closing reference, and guardian evidence.
Out of Scope Changes check	✅ Passed	The changes stay focused on documenting the storage location and recording the smoke-run artifact.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch kaizen/issue-131-readiness-review-run-and-record-a-real-sandbox-e

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fc6c0b48bf

ℹ️ 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".

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/smoke-runs/2026-07-04T07-49-09Z-issue-157.json`:
- Around line 19-20: The committed smoke-run artifact still contains
machine-local /Users/.../.kaizen paths, so sanitize all operator-specific
locations before saving the JSON. Update the artifact generation in this
smoke-runs evidence file to replace summaryPath, issueLogDir, verifyLogPath,
logPath, and artifactPath with portable, repo-relative, or placeholder values
that do not expose a local home directory. Keep the structure intact while
ensuring the persisted paths are durable across machines and do not leak account
details.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

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

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 3933677d-e158-4669-89e5-895227a97500

📥 Commits

Reviewing files that changed from the base of the PR and between e02a5db and fc6c0b4.

📒 Files selected for processing (2)

• docs/13-sandbox-smoke.md
• docs/smoke-runs/2026-07-04T07-49-09Z-issue-157.json

[s-hiraoku]

PR Guardian final status:

• Fix pushed: 87dbb2a sanitized committed smoke artifact paths so no operator-local /Users/... paths remain
• Review feedback addressed: replied to and resolved the Codex and CodeRabbit threads about local path leakage
• Validation: jq, npm test, npm run typecheck, and npm run build passed locally
• Checks: GitHub verify passed; CodeRabbit status is success
• Review threads: unresolved count is 0
• Mergeability: mergeable=MERGEABLE, mergeStateStatus=CLEAN
• Remaining blockers: none observed

[s-hiraoku]

PR Guardian final status (pass 1/5):

• Mergeability: mergeable=MERGEABLE, mergeStateStatus=CLEAN; PR is non-draft and non-conflicting.
• Checks: required verify passed on head 87dbb2a; CodeRabbit status is success.
• Watched CI runs: 28702588912 for fc6c0b4 and 28702681667 for 87dbb2a, both completed successfully via gh run watch --exit-status.
• Fixes pushed: 87dbb2a sanitizes the committed smoke artifact paths, replacing operator-local /Users/... values with portable run-relative paths and a repo-relative artifactPath.
• Feedback addressed: resolved/replied to the Codex and CodeRabbit threads about local path leakage; latest paginated GraphQL review-thread pass reports no non-outdated unresolved threads.
• Validation run: jq empty docs/smoke-runs/2026-07-04T07-49-09Z-issue-157.json, npm test, npm run typecheck, and npm run build passed.
• Skipped/non-actionable feedback: CodeRabbit generated finishing-touch checkboxes and review-limit notice did not identify a remaining code/doc defect; CodeRabbit also confirmed the path issue addressed.
• Remaining blockers: none observed.

Do not merge: monitoring only.