03 — AX-PROCESS Generator Patch (Phase 3)

What was patched

• Manifest v2 (v_rp_contract_generator_manifest_v2): the AX-PROCESS generated_leg_sql now unions three legs — the candidate source, a job:cut node whose count is the distinct cut-prefixed job_kind count from job_queue, and a workflows leg whose node is process_code and count is the workflow_steps count. source_kind relabelled candidate+jobcut+workflow.
• Generated backbone v2 (v_rp_universal_node_ui_contract_generated_v2): the AX-PROCESS portion materialises the same three legs, using the SAME count expressions the current v1 legs use, so counts match by construction.

Reliability / governance / class fields

The generated backbone carries provenance (source_view, leg_kind candidate/jobcut/workflow, is_registry_backed, is_synthetic). The decoration fields (reliability_label, governance_status, route, substrate) are applied by the shared decoration layer on the current stack and verified as 100% covered for these nodes (see doc 07). The substrate resolver for these legs is job_queue (job:cut) and workflow_steps (workflows), matching current.

Result

AX-PROCESS generated v2 = 22 nodes. Per-axis validation: current 22, generated 22, membership gap 0, count diff 0, axis_parity_pass true. Additive/reversible; v1 generator leg untouched (retained as regression sentinel — see doc 15 RGT2).