* Fix hook scripts to drain stdin before any early-exit path Generated agent hook scripts and missing-script launchers could exit successfully before consuming the payload written to their stdin, leaving the writer with a broken pipe (EPIPE/ERROR_BROKEN_PIPE) once the reader closed early. Capture stdin (or drain it via a shared epilogue/fast-path guard) before any whole-script success exit across all POSIX, batch, PowerShell, and Git Bash launcher variants, and add a cross-agent lifecycle test suite plus a live Electron verification script to guard the contract going forward. * Harden hook scripts against unreadable managed scripts and add a Claude/ - Extend the POSIX launcher guard to also require `[ -r ]`, not just `-f`/`-x`, so an executable-but-unreadable managed script still drains stdin instead of erroring or silently misbehaving. - Add a verifier case (`verifyClaudeDevinSkip`) that spins up a local HTTP server and confirms the Claude hook never forwards a request that Devin already imported, catching accidental double-forwarding. - Update installer-utils tests and stdin-lifecycle docs to match the new readable-file guard and the added verification case. * Fix hook-launcher verification to derive script paths from the installed Extract the quoted path from the launcher's `if [ -f '...'` clause instead of reconstructing it via join(home, ...), so missing/failing-script test cases can't silently fall through to the real script if the install layout changes. --------- Co-authored-by: Jinjing <6427696+AmethystLiang@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| plans | ||
| 2026-06-27-orca-mobile-manual-network-address-design.md | ||
| README.md | ||
| agent-hook-stdin-lifecycle.md | ||
| agent-session-resume-cli-evidence.md | ||
| direct-url-or-file-entry.md | ||
| feature-discovery-interaction-tracking.md | ||
| feature-education-retention-analytics.md | ||
| feature-education-state.md | ||
| git-compatibility.md | ||
| headless-linux-server.md | ||
| keyboard-layout-shortcut-dispatch.md | ||
| new-user-parallel-work-telemetry.md | ||
| opencode-commit-message-stdin.md | ||
| project-ordering-mode.md | ||
| reliability-gates-implementation-plan.md | ||
| reliability-pain-points-2026-06-30.md | ||
| ssh-typing-latency-under-relay-load.md | ||
| telemetry-availability.md | ||
| terminal-cold-park-reveal-cost.md | ||
| terminal-hidden-view-parking.md | ||
| terminal-model-view-contract.md | ||
| terminal-query-authority.md | ||
| terminal-side-effect-authority.md | ||
| terminal-switch-typing-lag-investigation.md | ||
README.md
Durable Docs
Keep this folder for versioned reference docs that are meant to survive past a single design or implementation pass.
What Goes Here
- Stable reference material.
- Public-facing docs that are not part of the root README.
- Docs that other checked-in files link to.
- Telemetry availability notes that dashboard authors need after the original design or implementation branch is gone. See Telemetry Availability.
- Headless Linux server setup for remote
orca servehosts. See Headless Linux Server. - Feature education state, interaction tracking, and retention analytics notes that define how contextual tours are persisted and measured. See Feature Education State, Feature Discovery Interaction Tracking, and Feature Education Retention Analytics.
- New-user parallel work telemetry notes that define how the parallel-work tour and setup guide should be measured against retention. See New User Parallel Work Telemetry.
What Stays Out
Ephemeral design notes, implementation sketches, and planning docs should stay as local Markdown files under docs/. They are ignored by default so they do not get checked in accidentally.