Repository navigation
fix: guide write delegation when Git history is unavailable - #12
Merged
Merged
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
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. |
ShadowfetchStudio
marked this pull request as ready for review
October 31, 2026 22:29
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A write-subagent request in a plain folder can send the parent into repeated failures: the worktree requires a commit, and the old diagnostic suggests creating one. On the Windows laptop, a public v2.3.0 model run then hit AppContainer's null-device restriction in external Git, repaired the fixture directly, but exhausted its task budget and exited unsuccessfully.
State the prerequisite in the tool description and task guidance, check it before preparing a worktree, and direct the parent toward its own editing tools or read-only agents. Preserve the sandbox boundary and retain normal write delegation for repositories with history. Add a regression covering plain folders, unborn repositories and committed repositories without silently creating history.
Prepare 2.3.1 metadata and document the failed public-installer run and existing external-Git limitation. Published v2.3.0 assets and tags remain unchanged. The website update remains gated on successful public-installer qualification.
Validation: Windows core unit suite passed (608 passed, 6 ignored), the existing context-budget regression passed without increasing its limit, and core all-target Clippy passed with warnings denied. Version metadata is consistent. These local code checks ran before the metadata-only 2.3.1 bump; macOS, UI, packaging and Windows build/unit/integration CI passed; Windows preview installer CI passed; Linux checks remain in progress. The corrected development live-model run passed in 479.59 seconds with the original 16k context and 100k token budget, successful sandboxed test execution, and all five unchanged original tests passing independently. This is development evidence; The preview installer installed successfully and passed clean-PATH startup and native WebView editor/settings checks; its model qualification passed in 562.51 seconds, including the observed sandboxed test and independent execution of the unchanged original tests. Public-release qualification remains pending. An earlier development attempt omitted the BusyBox runtime path and is explicitly not counted as qualified. Linux signature-harness tests require Linux /bin/bash; the macOS attempt was not counted as a pass.