The guard that couldn't find the same door

Description and use

Guard scripts in Oroboro Labs’ automation workflow misresolved file paths, causing false missing-file errors. Implementing a unified path resolver ensured consistent exit codes across directories, eliminating false alarms.

Problem

Different guard scripts resolved file paths inconsistently, causing false missing-file errors.

Outcome

All guard scripts now return consistent exit codes across directories, eliminating false missing-file alarms and improving reliability of the automation workflow.

Workflow

• 1. Create a resolver module that attempts path resolution in a fixed order: given path, workshop root, posts root, and filename search. 2. Import this resolver in all guard scripts. 3. Enforce single-candidate resolution; reject if multiple matches. 4. Exclude backup and receipt directories from filename search. 5. Run acceptance tests from three working directories to verify identical exit codes for all guards. 6. Update guards to use the resolver and adjust logic for historical mislabeled copies.

Evidence

The fix is a single resolver module that every guard now imports, trying paths in a fixed order: the path as given; relative to the workshop root; relative to the posts root; and finally a search for the filename — resolving only if exactly one candidate exists

Source

The acceptance test found its own homonym

Source