Implement steps 3 + 4 of issue #115 on top of the failure classifier, now
that bincraft v4.4.3 applies registry patches/makevars/configure_args to the
target build (not just dependencies), so a trial patched build is meaningful.
- refactor the classify helpers to expose a pure build_triage_report() and a
list-returning entry builder; failing-builds-report.R now renders from it
- add local/propose-patches.R (step 3, "propose, do not apply"): emit a
pre-filled registry.json entry for each classified, safe, unregistered
failure, validate the candidate set against a temporary merged registry,
and (only on request) --write it plus a proposals ledger, or --open-issue a
Forgejo tracking issue; the human gate and validator/trial-build acceptance
stay, and novel source diffs / unknown signatures are never proposed
- add local/trial-build-patch.R: isolated bincraft build of one package with
the registry applied (no upload/archive/metadata) as the pre-merge gate
- add local/proposal-tracking.R + local/proposal-tracking-lib.R (step 4):
signature hit rate, proposed-vs-merged, and retirement candidates, with the
pure helpers covered by tests
- teach validate-patches.R optional PATCH_DIR/REGISTRY_FILE overrides so a
candidate registry can be validated without touching the real one
- document the propose/trial-build/tracking workflow in local/patches/README.md
pat-s
8afa584da3