docs: add GRA-374 experiment artifact#255
Conversation
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
📝 WalkthroughDocumentation: GRA-374 Multi-CLI Installer Experiment Artifact
WalkthroughThis PR adds a research experiment documentation file for GRA-374, specifying a 7-day multi-CLI installer evaluation across Claude Code, Codex, Cursor, Hermes, and OpenCode. The document defines the success metric (≥80% passing), baseline (20%), runbook procedures, final results (verdict: DISCARD, 20% outcome), and filed follow-up work. ChangesGRA-374 Multi-CLI Installer Experiment
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
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 `@Gradata/docs/research/gra-374-multi-cli-install-success-rate.md`:
- Line 4: The experiment window "Window: 2026-05-12 to 2026-05-19" contradicts
the stated 7‑day duration; update the window string (or nearby sentence) to
either end at 2026-05-18 to be inclusive 7 days or add explicit wording that the
end date is exclusive (e.g., "2026-05-12 to 2026-05-19 (end date exclusive)");
apply the same change wherever the same window appears (the "Window: 2026-05-12
to 2026-05-19" text and any duplicate instance noted as "Also applies to:
10-10").
🪄 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: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 32098443-860d-4e0a-a335-49c9b4a2c3df
📒 Files selected for processing (1)
Gradata/docs/research/gra-374-multi-cli-install-success-rate.md
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)
- GitHub Check: pytest ubuntu-latest / py3.11
- GitHub Check: pytest windows-latest / py3.12
- GitHub Check: pytest macos-latest / py3.12
- GitHub Check: pytest windows-latest / py3.11
- GitHub Check: pytest macos-latest / py3.11
- GitHub Check: pytest ubuntu-latest / py3.12
- GitHub Check: pytest (py3.12)
- GitHub Check: pytest (py3.11)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2026-04-17T17:18:07.439Z
Learnt from: Gradata
Repo: Gradata/gradata PR: 0
File: :0-0
Timestamp: 2026-04-17T17:18:07.439Z
Learning: In PR `#102` (gradata/gradata), Round 2 addressed: cli.py env-first brain resolution (GRADATA_BRAIN > --brain-dir > cwd), _tenant.py corrupt .tenant_id overwrite, _env_int default clamping to minimum, and _events.py tenant-scoped fallback SELECT for dedup. All ruff and 99 tests green after these fixes.
Applied to files:
Gradata/docs/research/gra-374-multi-cli-install-success-rate.md
| # GRA-374: multi_cli_install_success_rate experiment | ||
|
|
||
| Status: evaluated — DISCARD | ||
| Window: 2026-05-12 to 2026-05-19 |
There was a problem hiding this comment.
Clarify the experiment window to match the stated 7-day duration.
2026-05-12 to 2026-05-19 reads as 8 days (inclusive), which conflicts with “quick 7-day experiment.” Please either adjust one date (e.g., end at 2026-05-18) or explicitly state exclusive-end semantics.
Proposed doc fix
-Window: 2026-05-12 to 2026-05-19
+Window: 2026-05-12 to 2026-05-18Also applies to: 10-10
🤖 Prompt for 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.
In `@Gradata/docs/research/gra-374-multi-cli-install-success-rate.md` at line 4,
The experiment window "Window: 2026-05-12 to 2026-05-19" contradicts the stated
7‑day duration; update the window string (or nearby sentence) to either end at
2026-05-18 to be inclusive 7 days or add explicit wording that the end date is
exclusive (e.g., "2026-05-12 to 2026-05-19 (end date exclusive)"); apply the
same change wherever the same window appears (the "Window: 2026-05-12 to
2026-05-19" text and any duplicate instance noted as "Also applies to: 10-10").
Summary
multi_cli_install_success_rateVerification
git diff --cached --checkbefore commitPaperclip: GRA-374