Skip to content

docs(sandboy): cross-link 007 loop-canvas for the gate/run contract - #183

Closed
PhysShell wants to merge 3 commits into
mainfrom
claude/loop-canvas-007-sandboy-mugo5y
Closed

docs(sandboy): cross-link 007 loop-canvas for the gate/run contract#183
PhysShell wants to merge 3 commits into
mainfrom
claude/loop-canvas-007-sandboy-mugo5y

Conversation

@PhysShell

Copy link
Copy Markdown
Owner

Что и зачем

Добавляет обратную ссылку в sandboy/README.md («Wiring into 007»): тот же per-step wrap описан в 007/docs/loop-canvas.md как поля канваса Actions / Limits / Observability, хук на стороне 007 — поле sandbox_policy на GateStep (forward-compatible, ещё не добавлено), а sandboy --report <json> — источник machine-readable evidence для Observability. Контракт интеграции теперь указывает в обе стороны. Только документация, поведение не меняется.

Тип изменения

  • feat — новая возможность
  • fix — исправление бага
  • docs — документация
  • refactor / chore / test / ci — без изменения поведения

Как проверено

  • python tests/run_tests.py
  • ruff check . и mypy
  • селфтесты затронутых скриптов (python scripts/<...>.py --selftest)

Docs-only: правка одного sandboy/README.md, кода не касается — гонять нечего. Проверил рендер ссылок/секций.

Связанные issue

Нет. Парная документация к 007 PR (docs/loop-canvas.md) — в приватном репо 007, не связывается через issue.

Чеклист

  • изменение покрыто тестом/селфтестом (или объяснено, почему нет) — docs-only, тестировать нечего
  • README/docs обновлены при необходимости
  • коммиты в conventional-commit стиле (feat:, fix:, docs: …)

🤖 Generated with Claude Code

https://claude.ai/code/session_01VNgUjrvwqwtXqe8URbJaQN


Generated by Claude Code

…n contract

The "Wiring into 007" section already describes the per-step wrap; point it
at 007/docs/loop-canvas.md, where the same slot is framed as the canvas
Actions/Limits/Observability fields. Docs only.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VNgUjrvwqwtXqe8URbJaQN
@coderabbitai

coderabbitai Bot commented Jul 5, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 20 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 4c1e23ac-34ce-48ad-8ab2-f3e5f97d0efd

📥 Commits

Reviewing files that changed from the base of the PR and between 5ea68da and dbe8702.

📒 Files selected for processing (1)
  • sandboy/README.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/loop-canvas-007-sandboy-mugo5y

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

Comment @coderabbitai help to get the list of available commands.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dab92f1256

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

Comment thread sandboy/README.md Outdated
PhysShell and others added 2 commits July 5, 2026 12:32
Codex review (PR #183): the wiring note described `sandboy --report <json>`
as if available, but `parse_args` accepts only `run`/`--policy`/`--` and
rejects any other flag (exit 2). Mark both integration hooks (`--report`
on sandboy, `sandbox_policy` on 007's GateStep) explicitly as Floor-1 work
that does not exist yet, and note the current stderr enforcement status.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VNgUjrvwqwtXqe8URbJaQN
Keep the two sides of the contract consistent: the 007-side bullet framed
`sandbox_policy` as plain "forward-compatible", but 007/docs/loop-canvas.md
now requires it to fail closed (schema bump) since silent unknown-field
tolerance fails open on a security control.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VNgUjrvwqwtXqe8URbJaQN

Copy link
Copy Markdown
Owner Author

Консолидировано в #190 (обратная ссылка sandboy → 007 loop-canvas вошла; формулировка про bypassPermissions для gate-шагов уточнена). Закрываю в пользу единого PR.


Generated by Claude Code

@PhysShell PhysShell closed this Jul 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant