Historical field note

This record preserves prior investigation or planning evidence. It is not a current operating contract; use the numbered book and current runbooks for instructions.

Assessment: task_7023d6a7ef6e4bbf8f6c2da523a4320f

Task: Investigate low-confidence dream-cycle repair finding dreamrepair:c045d7447b1b29bfc2deb42e38e39940 before changing skills or tools. Origin candidate: task_08f2dec144124edf99f32b9a8e254b21 (project=mac) Finding kind: failure_pattern — scope project — confidence low (1 record) Repo areas: mac, tests Assessment Date: 2026-07-16 Assessed by: fleet worker (investigation, no source/test edits)

Status: CLOSED — NOT ACTIONABLE; the supporting record is a verification-contract artifact, not a code defect

Finding Under Review

The dream cycle proposed a low-confidence failure_pattern supported by a single memory record: a prior audit of src/mac/fleet_deploy.py against tests/test_fleet_deploy_edges.py that was logged as a [failure]. The audit's own summary stated that "all eight imported symbols exist and exhibit exactly the asserted" behaviors — i.e. it found no defect, yet was recorded as a failure.

Ground Truth Observed

Measured in the task-owned worktree with the bootstrapped .venv (python3/git/gh present; pytest/coverage installed by python3 scripts/bootstrap-project.py).

1. Imported symbols exist and match the asserted contract

All eight symbols imported by tests/test_fleet_deploy_edges.py (SshTarget, canonicalize_mesh_ssh_target, cleanup_path_strings, cleanup_retention_plan, ensure_owner_only_directory, parse_ssh_target, shell_words, write_owner_only_file) are defined in src/mac/fleet_deploy.py with the semantics the tests assert (0o600 file mode, 0o700 directory mode, atomic write, retention-plan entries, pipe-delimited strings, mesh mDNS canonicalization).

2. Targeted edge tests

Command: .venv/bin/pytest tests/test_fleet_deploy_edges.py -q

Metric	Value
Result	20 passed, 0 failed

3. Module-scoped coverage — src/mac/fleet_deploy.py

Command: .venv/bin/python -m coverage run --branch --source=mac.fleet_deploy -m pytest tests/test_fleet_deploy_edges.py

Metric	Value
Coverage	80.00% statements+branches
Uncovered	subprocess/error paths (_tailscale_status, live scp_args/ssh_args port branches, mesh multi-match guards)

The uncovered lines are defensive subprocess and error branches, not behaviors the edge-case contract asserts. This is expected for an edge-focused suite and is not a coverage regression.

Finding

• Is the finding actionable? No. There is no reproducible failure in the source or tests. The targeted edge suite passes and every imported symbol exists with the asserted behavior.
• Evidence gap. The single supporting record is a repo_change task that reached a correct "no defect" conclusion but was marked [failure] because it produced no committed file — a verification-contract artifact, not a product defect. One such record at low confidence is insufficient to justify changing any skill, tool, or module.
• Remediation. None to product code or tests. This assessment file closes the finding with its reason and evidence gap.

Note

This assessment file is the committed deliverable for an investigation-only task. Prior attempts established the same ground truth but failed contract verification because they produced no committed file (repo_change evidence requires changed files). Per the task instruction, no source or test files were modified; generated coverage artifacts (coverage.json, .coverage) remain gitignored.