refactor: rename agentfs to vfs across runtime, tooling, and docs - #4
Merged
Conversation
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
This was referenced Jul 27, 2026
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.
Description
What
Renames the product surface from
agentfstovfs: workspace crates, CLI binary and command output, validation tooling, benchmarks, and docs. 241 files, net -133 lines, no behavior change.Why
The runtime stopped being agent-specific;
vfsis the name the handoff stack (pack/seed/run PRs above this one) ships under, so the rename lands first to keep those diffs readable.How
Four mechanical commits, one per surface: workspace runtime, product docs, validation tooling, and the NFS write-handle magic constant.
Four follow-up commits repaired main's pre-existing macOS CI breakage, surfaced once this PR targeted main:
07fea79and863e5a7cfg-gate Linux-only helpers (wait_for_mount, the proc-file writers,report_checkpoint,KnobClass::KillSwitch),1183037restores publicvfs_mount::unmountand the struct-literalMountOptsidiom indarwin.rs, and814d725repairs the.gitignoreIcon[glob and ignores legacy.agentfs/dirs.Stack (merged bottom-up 2026-07-28, vfs main @
3b2af42):Related Issue
Part of AC-768
Reviewer Guide
Diff shape: ~95% mechanical identifier/path renames; ~5% docs prose. Skip: benchmark scripts beyond spot checks.
Review depth: Skim. The real check is completeness, not correctness:
rg -i agentfson the branch should only hit historical spec filenames under.agents/specs/.Read order: commit-by-commit; each commit is one surface.
Risk & Impact
One deliberate break: the NFS write-handle magic changes
AFSWRIT\0->VFSWRIT\0, so write handles minted by a pre-rename server are invalid after upgrade (clients re-open; no data loss). Everything else is a pure rename; the remaining failure mode is a missed reference in a script or doc, covered by the rg audit above.Verification
Behavior verified. Workspace builds and the CLI test suite pass at
debbd50;rg -i agentfsresiduals are confined to dated spec filenames.Regression coverage. Existing suites unchanged; a missed rename in tooling fails the shell suites directly.
Not tested. N/A, rename only.
Standard validators. cargo build/test and CLI shell suites clean.