docs: generalize skip flag references and fix fuse_probe doc

- Use generic pdu_test_skip_* wording in AI instructions instead of
  naming the specific cross_device flag
- Mention that panic messages include the specific skip flag
- Fix fuse_probe doc: say "exists" not "is accessible" for /dev/fuse,
  say "tool names" not "tool paths" for the return value
- Regenerate AI instruction files

https://claude.ai/code/session_01LfpnUZrgq93MVZgA3KVqE6

Author: claude

.github/copilot-instructions.md

@@ -19,4 +19,4 @@ Read and follow the CONTRIBUTING.md file in this repository for all code style c
 - Run `FMT=true LINT=true BUILD=true TEST=true DOC=true ./test.sh` to validate changes. If a test fails with a hint about `RUSTFLAGS` and `--cfg pdu_test_skip_*`, follow the hint and rerun with the suggested flags.
 - **ALWAYS run the full test suite** (`FMT=true LINT=true BUILD=true TEST=true DOC=true ./test.sh`) before committing, regardless of how trivial the change seems — this includes documentation-only changes, comment edits, config changes, and refactors. The test suite checks formatting, linting, building, tests, and docs across multiple feature combinations; any type of change can break any of these checks.
 - Set `PDU_NO_FAIL_FAST=true` to run all checks instead of stopping at the first failure — this lets you see which checks pass and which fail
-- Some integration tests require external (non-Cargo) dependencies: `squashfs-tools`, `squashfuse`, `fuse3` (see CONTRIBUTING.md for details). If unavailable, skip with `RUSTFLAGS='--cfg pdu_test_skip_cross_device'`
+- Some integration tests require external (non-Cargo) dependencies (see CONTRIBUTING.md for details). If unavailable, the tests will panic with a hint showing the `RUSTFLAGS='--cfg pdu_test_skip_*'` flag to skip them

AGENTS.md

@@ -19,4 +19,4 @@ Read and follow the CONTRIBUTING.md file in this repository for all code style c
 - Run `FMT=true LINT=true BUILD=true TEST=true DOC=true ./test.sh` to validate changes. If a test fails with a hint about `RUSTFLAGS` and `--cfg pdu_test_skip_*`, follow the hint and rerun with the suggested flags.
 - **ALWAYS run the full test suite** (`FMT=true LINT=true BUILD=true TEST=true DOC=true ./test.sh`) before committing, regardless of how trivial the change seems — this includes documentation-only changes, comment edits, config changes, and refactors. The test suite checks formatting, linting, building, tests, and docs across multiple feature combinations; any type of change can break any of these checks.
 - Set `PDU_NO_FAIL_FAST=true` to run all checks instead of stopping at the first failure — this lets you see which checks pass and which fail
-- Some integration tests require external (non-Cargo) dependencies: `squashfs-tools`, `squashfuse`, `fuse3` (see CONTRIBUTING.md for details). If unavailable, skip with `RUSTFLAGS='--cfg pdu_test_skip_cross_device'`
+- Some integration tests require external (non-Cargo) dependencies (see CONTRIBUTING.md for details). If unavailable, the tests will panic with a hint showing the `RUSTFLAGS='--cfg pdu_test_skip_*'` flag to skip them

CLAUDE.md

@@ -19,5 +19,5 @@ Read and follow the CONTRIBUTING.md file in this repository for all code style c
 - Run `FMT=true LINT=true BUILD=true TEST=true DOC=true ./test.sh` to validate changes. If a test fails with a hint about `RUSTFLAGS` and `--cfg pdu_test_skip_*`, follow the hint and rerun with the suggested flags.
 - **ALWAYS run the full test suite** (`FMT=true LINT=true BUILD=true TEST=true DOC=true ./test.sh`) before committing, regardless of how trivial the change seems — this includes documentation-only changes, comment edits, config changes, and refactors. The test suite checks formatting, linting, building, tests, and docs across multiple feature combinations; any type of change can break any of these checks.
 - Set `PDU_NO_FAIL_FAST=true` to run all checks instead of stopping at the first failure — this lets you see which checks pass and which fail
-- Some integration tests require external (non-Cargo) dependencies: `squashfs-tools`, `squashfuse`, `fuse3` (see CONTRIBUTING.md for details). If unavailable, skip with `RUSTFLAGS='--cfg pdu_test_skip_cross_device'`
+- Some integration tests require external (non-Cargo) dependencies (see CONTRIBUTING.md for details). If unavailable, the tests will panic with a hint showing the `RUSTFLAGS='--cfg pdu_test_skip_*'` flag to skip them
 - `gh` (GitHub CLI) is not installed — do not attempt to use it

CONTRIBUTING.md

@@ -377,7 +377,7 @@ On Debian/Ubuntu:
 sudo apt install squashfs-tools squashfuse fuse3
 ```
 
-Tests that need these tools will panic with a diagnostic message if they are missing. To skip them instead, set:
+Tests that need these tools will panic with a diagnostic message if they are missing. The panic message includes the specific `RUSTFLAGS='--cfg pdu_test_skip_*'` flag to skip the test. For example:
 
 ```sh
 export RUSTFLAGS='--cfg pdu_test_skip_cross_device'

template/ai-instructions/shared.md

@@ -19,4 +19,4 @@ Read and follow the CONTRIBUTING.md file in this repository for all code style c
 - Run `FMT=true LINT=true BUILD=true TEST=true DOC=true ./test.sh` to validate changes. If a test fails with a hint about `RUSTFLAGS` and `--cfg pdu_test_skip_*`, follow the hint and rerun with the suggested flags.
 - **ALWAYS run the full test suite** (`FMT=true LINT=true BUILD=true TEST=true DOC=true ./test.sh`) before committing, regardless of how trivial the change seems — this includes documentation-only changes, comment edits, config changes, and refactors. The test suite checks formatting, linting, building, tests, and docs across multiple feature combinations; any type of change can break any of these checks.
 - Set `PDU_NO_FAIL_FAST=true` to run all checks instead of stopping at the first failure — this lets you see which checks pass and which fail
-- Some integration tests require external (non-Cargo) dependencies: `squashfs-tools`, `squashfuse`, `fuse3` (see CONTRIBUTING.md for details). If unavailable, skip with `RUSTFLAGS='--cfg pdu_test_skip_cross_device'`
+- Some integration tests require external (non-Cargo) dependencies (see CONTRIBUTING.md for details). If unavailable, the tests will panic with a hint showing the `RUSTFLAGS='--cfg pdu_test_skip_*'` flag to skip them

tests/one_file_system.rs

@@ -86,10 +86,10 @@ struct FuseTools {
 /// Verifies:
 /// 1. `mksquashfs` binary exists
 /// 2. `squashfuse` binary exists
-/// 3. `/dev/fuse` is accessible
+/// 3. `/dev/fuse` exists
 /// 4. `fusermount3` (or `fusermount`) binary exists
 ///
-/// Returns `Ok(FuseTools)` with the discovered tool paths, or `Err` with a diagnostic message.
+/// Returns `Ok(FuseTools)` with the discovered tool names, or `Err` with a diagnostic message.
 fn fuse_probe() -> Result<FuseTools, String> {
     which("mksquashfs").map_err(|error| {
         format!("`mksquashfs` not found: {error}. Install squashfs-tools for your platform.")