Problem / Why
Merged specifications are treated as binding constraints by every downstream feature, so a factual error in one propagates. Feature #464 had to reconcile both of these against the real code before it could execute, and recorded the disagreement in its own spec.md sections R-1 and R-2 rather than silently following the incorrect text. Leaving the errors in place means the next feature repeats that work, or worse, follows them.
Implementation Intent
Amend both specifications in place with a dated correction note that states what the original text asserted, what the code actually does, and the evidence for the correction. Do not delete the original assertion; a correction that erases the error loses the audit trail of why the belief was held.
Acceptance Criteria
Dependencies / Risks
Documentation-only, so the risk is low, but the corrections must themselves be verified against the code rather than copied from #464's reading. Feature #464 also observed that MoveMailAsync is not implemented by EfcItemController on the integration base, contrary to a statement in its own upstream briefing; that observation should be re-checked before being written down as fact.
Verification Steps
Evidence Checklist
Source
From: docs/features/potential/2026-08-27-upstream-spec-corrections-484-r1-and-444-r2.md
Problem / Why
Merged specifications are treated as binding constraints by every downstream feature, so a factual error in one propagates. Feature #464 had to reconcile both of these against the real code before it could execute, and recorded the disagreement in its own
spec.mdsections R-1 and R-2 rather than silently following the incorrect text. Leaving the errors in place means the next feature repeats that work, or worse, follows them.Implementation Intent
Amend both specifications in place with a dated correction note that states what the original text asserted, what the code actually does, and the evidence for the correction. Do not delete the original assertion; a correction that erases the error loses the audit trail of why the belief was held.
Acceptance Criteria
docs/features/active/qfc-item-controller-defects-484/spec.mdR-1 carries a dated correction, with the original claim preserved.docs/features/active/quickfiler-keyboard-action-defects-444/spec.mdR-2 carries a dated correction, with the original claim preserved.Dependencies / Risks
Documentation-only, so the risk is low, but the corrections must themselves be verified against the code rather than copied from #464's reading. Feature #464 also observed that
MoveMailAsyncis not implemented byEfcItemControlleron the integration base, contrary to a statement in its own upstream briefing; that observation should be re-checked before being written down as fact.Verification Steps
Evidence Checklist
Source
From: docs/features/potential/2026-08-27-upstream-spec-corrections-484-r1-and-444-r2.md