Release
v3.3.2
floorboardCoupling floors now apply to Argus's own remediations: when the advisory fix lands below the floor you vetted, the fix moves to the floor — one coherent remediation instead of a resolve-manually warning.
Highlights
- 01
The floor is your vetting statement
A coupling floor says "with the trigger at this wave, the companion must be at least Y — we tested that pair." That holds regardless of who moves the version, so a remediation planned below the floor is raised to it, clearing the advisory and honouring the vetted pair in one patch.
- 02
Narrow by design
Only single-target direct fixes rendered at the root POM are raised, and never to a floor that is itself advisory-affected. Parents, anchors, family BOMs and module-routed reactor plans keep the visible resolve-manually warning, and ceilings and offlimits gate exactly as before.
Full notes
Fixed
- A coupling floor raises the companion's own remediation (key and RM reference re-minted so patch, marker and report agree); reg-097 covers the scenario end to end.
- Merge requests no longer claim "the pin has been removed" for overrides withdrawn within the same run; those render under a new 'Resolved without a pin' section, and 'Also removed' is reserved for deletions visible in the diff (reg-098).
- Companion skips that are satisfied log as information instead of warnings.