Execute Verification: #449 Word result preservation

Final local acceptance — 2026-10-09

#449의 원래7 기준을 Execute Verification이 직접 대조하고 CLOSED로 재조회했다. 정확한 local develop a76f571d0a9dcce4dc576a813b0a9047eee94b79, tree ed05647990cd6485d53b25a22eb3153ff6f2426d다. source35와22 artifact hashes 모두 일치, old genuine/current compiled77 일치, extracted native decoder 본문 동일을 독립 확인했다. Final preflight53988 및 integrated Word19/API3/producer66/semantic42/core35, compiled17, button7/3 real Chromium이 통과했다.

기존 genuine preservedv16과 changed case inside aggregatev9는 각 이전 source의 증거다. final-tree genuine/mixed-list UI replay로 다시 표시하지 않는다. 원래 실패와 Chrome155/physicalIME 한계는 남긴다. #428/#431 actual restored-new-ID trusted confirmation/legacy execution UI 및 전체 Goal/alpha/출시는 미완료다. 다음 기존 이슈는 #423의 현재-source 수락 대조다. 아래 이전 진행 기록은 이력이다.

Current execution — 2026-10-09

검증 실행 로드맵은 Execute가 직접 관리한다. 현재 상태는 #449 Current work record에 있다.

실제 보존 v16 사례와 실제 변경 v9 사례를 확인했다. 보존은 passed, 보호 문단 변경은 failed 영수증을 만들었다. 보존 v16은 full native/model/history/selection/reference 보존, 재열기, 실제 응답 손실의 정확한 재시도, 동일 DB/API/browser 재시작, latest input와 public x+24 수식 초안 거부, late account response retirement와 cleanup까지 통과했다. 이는 SDK browser 145 범위다. Chrome 155 close 실패는 남긴다.

후속 controlled API/전용 PostgreSQL/JWKS 검사 17개는 복사 문서의 원본 결과 상속 거부와 복원된 새 revision의 과거 영수증 유지까지 통과했다. v16 및 후속 harness의 필수 Node22/pnpm8.15 gate 통과를 확인했다. 실제 UI 복사·복원 워크플로나 전체 제품 완료로 일반화하지 않는다. 후속 source review에서 button/native mixed receipt를 기존 button client가 읽지 못하는 AC-6 회귀를 확인했다. Editor의 정확한 3개 client/decoder 파일 failing test와 수정 결과는 pending이다. 별도 기존 registered-button executor/private PostgreSQL 회귀는 7 checks/3 actual Chromium invocations로 통과했다. migration catalog의 원래 assertion 실패는 보존한다. 추가 service harness의 source33 및 이후 client 수정을 위한 gate, 순차 통합·원래 7개 기준 대조가 남아 #449는 OPEN이다.

word-paragraph-preserved/v1은 정확한 authored requirement를 사용한다. 현재 bounded evaluator는 그 문장의 유효한 visible formatting을 허용하면서 full native 보호 문단 비교를 유지한다. 아래의 초기 source candidate와 당시 미검증 기록은 이력을 위해 보존한다. 최신 구현·검사 상태는 위 이슈 기록을 따른다.

Current scope

Owner: Execute Verification. This page records the implementation contract for Issue #449. It does not approve a product release or close the issue.

The first bounded evaluator is word-paragraph-preserved/v1. A person authors the exact plain requirement sentence Preserve the linked decision paragraph exactly as pinned. and explicitly confirms that requirement and pinned decision context through the existing #428 confirmation path. The linked decision's uniquely bookmarked paragraph is the protected target. An arbitrary confirmed requirement cannot trigger this preservation check. A later deliberate check selects one Project work, result, attempt, and applied output. The check does not modify the document, confirm a criterion, accept a proposal, or apply a generated edit.

Server contract

POST /v1/tenants/:tenantId/documents/:documentId/criterion-verifications/work-results accepts only:

{
  "schemaVersion": 1,
  "projectId": "UUID",
  "workId": "UUID",
  "attemptId": "UUID",
  "resultId": "UUID",
  "confirmationId": "UUID",
  "expectedOutputRevision": 3,
  "expectedOutputHash": "64 lowercase hex characters",
  "authorityEpoch": "current server context value",
  "idempotencyKey": "caller-generated stable operation key",
  "evaluator": { "id": "word-paragraph-preserved", "version": 1, "definition": "registered server definition" }
}

The server validates the exact registered evaluator and rejects extra fields. It derives actor, time, input, output, comparison, outcome, and digest from current authorized records. The client cannot submit a pass flag, output text, actor, executor, or clock. The existing fictional button specimen path remains separate.

The service checks Project work/result/comment links, the stored attempt's applied phase and Word target, the original Project pin, the exact confirmed pre-work snapshot, and the current saved output revision and hash. It requires the stored expected output bytes to equal the saved document. It uses the existing tenant authority, advisory key lock, immutable verification table, retry key and private read path. A completed retry returns the same result under current authority; a reused key for another request is rejected.

The evaluator compares the complete uniquely bookmarked decision paragraph from the confirmed full native decision pin with the saved result. A change to its text, marks, attributes, child nodes or references fails. A pass also requires the same business identities and the Word pair reader's full native reference context. Missing or duplicate bookmarks, invalid native files, changed business identity, an unregistered condition and changed reference context are unsupported. This result proves only this declared preservation condition.

Evidence and dependencies

The isolated source baseline is accepted local a6151b1e6fbd55e0ebd743043495aab79415a8c6. The seven-file source candidate is local 2d3fea156f97d24bb58b02d59db0ee638147f265; the first two-file test/manual follow-up is 0856a07d0a44d1796c6fb7eaf7fcc7e32e8c1567. Editor supplied the disjoint native-target candidate 84267fd301fb5ff8c455e819ed81c06cce45258e. Verification then added the two-file test/manual follow-up 2e243b9390528cf77421ff7778ea68c426be1be2 against a local combination. These commits have easylogic as author and committer. Correction: the prior statement that ProjectExecutionStore supports only Note was wrong. The accepted source, also present at current accepted develop 05ba7596220fee267160842e569a9af38ab505d8, supports a Word comment target through native capture, expected full Word output, explicit acceptance, exact saved snapshot and acknowledge phase applied. Existing project-execution.postgres.integration.mjs contains a controlled Word path. This is static source and test existence, not a fresh #449 run, live provider, desktop UI, OIDC/PostgreSQL authority, restart or native-history proof. Controlled synthetic #449 attempt tests prove local evaluator and store refusal/record logic only.

The #423 point-bookmark paragraph has both a bookmark-anchor child and an inline-text child. The original Word target rule refused it with unsupported_target. Execute Editor candidate 84267fd301fb5ff8c455e819ed81c06cce45258e changes the exact four-file server/client target path. In a separate combined local source check, the existing Word producer captures this protected target and produces a changed native snapshot. The preservation evaluator returns failed; a separate unprotected edit leaves the decision intact and returns passed. The combined controlled service tests passed 53 and API tests passed 3. These are local source tests, not a joined applied attempt, private PostgreSQL/OIDC, browser UI, restart or full native-history pass.

On the exact follow-up candidate, Node 22.22.0 / pnpm 8.15.0 pnpm preflight finished exit 0 with unchanged debt budgets. The office API build on the initial seven-file candidate finished exit 0. Focused service tests passed 20 and focused API tests passed 6, including the unchanged #431 tests. The first test invocation could not resolve unbuilt package exports; the dependency build resolved that setup error. The first new fixture mutated a nested historical pin; the fixture was corrected to change only current native content. The first full preflight then reported 17 new test TypeScript errors from unguarded JSON fixture fields; explicit object guards removed them. The follow-up native fixture's first test-type check exposed two unknown-content errors; local object guards removed them before the final full preflight passed. No assertion or budget was lowered. On the local combined Editor and Verification candidate, Node 22.22.0 / pnpm 8.15.0 pnpm preflight exited 0 with the existing source and test type budgets. Focused service tests passed 53/53 and API tests passed 3/3. The controlled result remains below product acceptance.

Integration owns the shared registration, API/private PostgreSQL/browser checks and serial local develop. Reuse the existing Word producer; do not create another one. The exact Editor UI consumer and a real joined verification run remain pending. The original #449 acceptance remains pending until genuine author → confirm → apply → deliberate check → reopen, unchanged/changed native outcomes, current authority, recovery, and affected integrated checks run on exact accepted source. #431 fictional specimen behavior and evidence remain intact. #420 Apply stays unavailable; #434 and Yorkie stay paused; mobile and physical OS IME are separate.