fix(scorecard): align text renderer with JSON via per-row pipeline

[brettdavies]

Summary

The --output text view, its badge, and the process exit code were computed from raw probe results, while --output json already ran the schema-0.6 per-row + antecedent-propagation pipeline. So the terminal printed probe ids (p2-schema-print) instead of requirement-row ids (p2-must-schema-print), could never render [N/A ] (only propagation produces n_a), and its row count, badge score, and exit code could disagree with the JSON the site and scorer consume. A human auditing bat saw [FAIL] … (p2-schema-print) for a MUST the tool is actually exempt from.

This routes all three text-side surfaces through the same pipeline. The fan-out + propagation pair that build_scorecard inlined is extracted into build_row_results, and main::run derives one per-row set that feeds format_text, compute_badge, and exit_code. Text and JSON now agree on the row set, counts, badge score, and exit code. The JSON path is byte-identical and the schema stays 0.6.

Changelog

Changed

• anc audit (text mode) now reports the same requirement rows as --output json: requirement-row ids (p2-must-schema-print) instead of probe ids, with the requirement tier (must/should/may) shown on each row.
• The process exit code now reflects the per-row result set in both output modes. A requirement that collapses to n_a because its conditional prerequisite is opt_out no longer forces a non-zero exit; only a live Fail/Error exits 2 and a live Warn exits 1.

Fixed

• Text mode now renders [N/A ] (with antecedent evidence) for conditional requirements whose prerequisite was opted out, instead of showing a misleading [FAIL] on the probe id. Text row count and badge score now match --output json.

Type of Change

• fix: Bug fix (non-breaking change which fixes an issue)

Related Issues/Stories

• Story: n/a
• Issue: n/a
• Architecture: docs/plans/2026-05-27-002-fix-text-renderer-per-row-parity-plan.md
• Related PRs: feat(scorecard): 7-status taxonomy, per-row emission, antecedent propagation (schema 0.6) #62 (per-row pipeline + schema 0.6, JSON path only)

Testing

• Unit tests added/updated
• Integration tests added/updated
• Manual testing completed
• All tests passing

Test Summary:

• New unit tests: build_row_results_fans_out_then_propagates, exit_code_drops_to_zero_when_consequent_propagates_to_n_a, text_and_json_agree_on_a_propagated_conditional_row (bat-shaped fixture asserting consequent shows n_a not fail, row counts match, badge scores match).
• New integration test: test_text_and_json_agree_on_row_count_and_exit_code audits ls in both modes and pins text row count == JSON results.len() and exit-code parity, catching any revert that feeds the text renderer raw probe results.
• Existing format_text_* / format_text_raw / R4 audit-profile masking tests pass unchanged.

Files Modified

Modified:

• src/main.rs: derive one per-row projection after the principle filter; feed it to format_text, compute_badge, and exit_code.
• src/scorecard/mod.rs: add build_row_results; build_scorecard calls it; format_text renders the tier suffix; consolidate the Level→token mapping behind Level::as_str.
• src/principles/registry.rs: add Level::as_str as the single source of truth for the must/should/may token.
• tests/integration.rs: text/JSON row-count + exit-code parity guard.
• docs/plans/2026-05-27-002-fix-text-renderer-per-row-parity-plan.md: status proposed → completed.

Created:

• None.

Renamed:

• None.

Deleted:

• None.

Breaking Changes

• No breaking changes

The CLI surface and JSON schema are unchanged. The exit-code semantics shift for one edge: a tool that raw-Fails a check whose requirement row propagates to n_a now exits 0/1 instead of 2. That is the corrected behavior (the requirement does not apply), it matches what the JSON summary already reported, and anc is 0.x pre-launch. The --audit-profile masking path (plan R4) is independent and unchanged.

Deployment Notes

• No special deployment steps required

Post-Deploy Monitoring & Validation

No additional operational monitoring is required because anc is a local CLI with no runtime service. The only downstream consumer is agentnative-site, which reads the JSON scorecard; the JSON path is byte-identical (schema stays 0.6), so there is no consumer impact. Spot-check after merge: anc audit --command bat (text) shows [N/A ] … (p2-must-schema-print) (must) and no [FAIL] … (p2-schema-print), and anc audit --command bat / --output json agree on exit code.

Checklist

• Code follows project conventions and style guidelines
• Commit messages follow Conventional Commits
• Self-review of code completed
• Tests added/updated and passing
• No new warnings or errors introduced
• Changes are backward compatible (or breaking changes documented)