Execute Workspace 449 Word Approval

Execute Workspace: #449 Word approval value guard

Scope and owner

This manual records the Office Workspace client correction for Issue #449. Execute Workspace owns only packages/office-workspace/src/connected-work-control.tsx and packages/office-workspace/test/connected-work-approval.test.ts for this candidate. Execute Integration owns local develop, the shared browser/API/private PostgreSQL run, and product acceptance remains open.

Exact accepted base: local develop 927be2053c1d9ee5d2fa5fa84b3e824feed5fff0. Immutable local candidate: ffa3859a51a29bc948e738405cc99023a5ccb030, tree 83b7c01647b6ca63556a1b2e61ca4a2737070631, branch codex/449-word-approval-value. Product code has not been pushed or opened as a PR.

Actual failure and correction

A genuine two-profile Word run reached server acceptance (POST 200), then the client showed the approval-changed error before native apply/save. Integration compared the two actual accepted rows in the same disposable PostgreSQL with a read-only transaction and rolled it back. The before/accepted input and proposal were value-equal, and ID, actor, expected snapshot text and hash matched. JSON.stringify differed only because JSONB reordered object keys. This evidence is retained at /Users/user/.codex/visualizations/2026/10/09/449-word-shared-integration-v1/actual-accepted-jsonb-diagnosis-v3.json.

The client now uses its existing recursive sameValue comparison for Word input and proposal. JSON object key order may differ. Array order, scalar values, and raw native snapshot strings still must match. Exact attempt, actor, document and expected snapshot identity/hash checks, Note binding, current host/selection capture and ABA guards remain in place.

Verification and remaining work

An original-source controlled test failed for an equal Word attempt with reordered object keys: 16/17 focused cases passed, and native apply stayed at zero. After the correction, focused tests passed 17/17 and the complete Office Workspace suite passed 160/160. Negative cases still reject changed native bytes, pin order, proposal array order, false/null metadata, and produce no native effect. Node 22.22.0 / pnpm 8.15.0 pnpm preflight exited 0 with unchanged budgets and zero new lint diagnostics.

The corrected candidate was handed directly to Execute Integration for serial import and genuine rerun. This source-level correction does not prove native application, the full original #449 acceptance, or release. See the scoped Issue record.

Guard successor

Planner confirmed the same two-file scope. A test-only successor 0a61512170bf5d9f0c0cf7c454a4f6b0ce4366da (tree ea40553e519bbc362fc137ecf2c13cda725363f2) keeps the original source commit immutable. It adds no product source change. It verifies rejection with zero native effects for an extra input key, changed proposal replacement, changed input or expected snapshot hash, changed actor or document ID, and selection ABA during awaited server acceptance. The focused approval test now passes 24/24, the full Workspace suite passes 167/167, and Node 22.22.0 / pnpm 8.15.0 full preflight exits 0 with unchanged budgets. Execute Integration received the clean successor as the final candidate. Successor Issue record.

Additional isolated affected checks on the same candidate passed: Word connected native proposal 8/8, Word feedback recovery 13/13, Office client project 7/7, and Office client feedback recovery 14/14. The Word test printed an EditorViewDOM selection-retry diagnostic but passed all assertions. Shared genuine runtime checks remain with Integration.