v0.5.5 — Status Command Fixes

Highlights

This is a small, targeted patch closing out the last two items from the v0.5.4 audit — both isolated to status_cmd.

Fixed

• envguard status --verbose / -v crashed with TypeError — a debugging aid added to surface configuration warnings called Rich's Console.print() with an unsupported file keyword argument, causing status --verbose to fail every time instead of showing the intended warning. This has been corrected, and --verbose/-v now print configuration warnings cleanly without error.

• status silently hid configuration warnings — a repository with a typo'd or unrecognized key in .envguard.yml (e.g. disbaled_rules instead of disabled_rules) was correctly flagged by doctor, but status gave no indication anything was wrong, reporting Configuration: VALID regardless. status now surfaces the same warning doctor does — in both plain and verbose output — and the Configuration row in the status table correctly reflects WARNING when a configuration issue is present, instead of VALID.

Verified in this release

• Reproduced both issues live against v0.5.4 before the fix, and reconfirmed both are resolved in v0.5.5 using the same reproduction steps.
• status and doctor now agree on configuration validity in every tested case, closing the loop on the broader status/doctor consistency work from v0.5.3 and v0.5.4.

---

Status after this release: every bug identified across the v0.4.0 → v0.5.4 audit cycle (18 findings total) is now resolved. No known open issues heading into v0.6.0.