feat(reference-host): add buyer integration safety fixtures

[seonghobae]

Refs #377.

Authority and product boundary

Protected main is the only shipped-source authority. This Draft is the existing Inkspan writer for the reference-host buyer journey; live head/base/ancestry/review/check state must be refetched before every lifecycle action rather than copied from older snapshots.

Inkspan remains standalone and provider-neutral. Hosts own transport, authentication, authorization, tenancy, durable persistence, credentials, retention, deployment, durable audit, collaboration-provider / Y.Doc lifecycle policy, model policy, and durable PDF/export authority. The package requires no service, database, network, credential, or model; model/proposal output remains untrusted data.

Implemented active-PR scope

This lane covers host-owned strong-validator persistence/recovery, revision-gated delayed proposals, autosave lifecycle projection, host-created Y.Doc lifecycle and provider replacement/teardown, per-provider-generation host authorization placement, public CSS/font entrypoints, native-form serialization/reset/submission, a deterministic server-safe application shell plus narrow client hydration boundary, read-only/narrow-viewport/print/forced-colors browser journeys, exact-packed package consumption, and a bounded exact-packed Markdown-to-DOCX acquisition journey.

The native-form boundary exposes one synchronous durable-submission admission predicate, shouldBlockReferenceHostFormMutation(), and binds both submit and reset handlers to that predicate rather than deferred React presentation state. The same-turn regression starts an authorized durable submission, proves the synchronous single-flight gate is already acquired while the queued saving presentation commit has not run, and proves a form mutation is rejected in that interval. Read-only remains an independent fail-closed host policy input.

Same-turn native-form TDD lineage

• RED 9536306b1258a75415de9e7a8a5616a2e56780d: the shared synchronous-admission contract did not yet exist and exact-head CI failed.
• GREEN da627ef85b78344cbbcfae28f9626af84fe37bef: added shouldBlockReferenceHostFormMutation(readOnly, isDurableSubmissionInFlight) with presentation state excluded from mutation authority.
• Integration 37cfc42e1ac86576d98d96f970a0ee9bdfd70bca: bound both native submit and reset handlers to the synchronous admission contract.
• Current exact branch head at the latest pre-write refetch remains 1fb2d317838ff0ed71001d470af650692ebd36b2.

Cross-lane Markdown failure: corrected ownership state

Exact-head CI 32864768290 is a valid RED reproduction for this reference-host generation: typecheck passed, the native-form tests passed, Office and browser jobs passed, but src/referenceHostFrameworkFreePackedBoundary.test.ts failed because packed /markdown accessed a poisoned ambient globalThis.window accessor.

That defect is not current #176 behavior. Draft #176 remains the sole writer for the public Markdown/serialization boundary and its current exact head e1345c45ba9bf8e75bdab8ad7f56c7d7437f1470 contains the narrow repair. #176 records exact-current GREEN CI 32871290927, including successful packed ESM/CJS consumers under the hostile ambient-window regression. Older prose saying #176 still contains the defective typeof window authority probe is superseded.

#381 must therefore inherit/reconcile the existing #176 repair and revalidate it; it must not implement a competing Markdown fix.

Fresh exact state at this convergence

Immediately before this PR-state correction:

• protected main: 128a239f8b71ca16add4b9e15e21752d1ad63ff0;
• feat(reference-host): add buyer integration safety fixtures #381 head: 1fb2d317838ff0ed71001d470af650692ebd36b2;
• current-main comparison: merge base 3b38ead2d00f44eb578d0689087b9293b3dabe1e, 258 ahead / 156 behind; GitHub currently reports this PR non-mergeable;
• fix(reliability): harden public Markdown and local serialization boundaries #176 head: e1345c45ba9bf8e75bdab8ad7f56c7d7437f1470;
• feat(reference-host): add buyer integration safety fixtures #381 versus fix(reliability): harden public Markdown and local serialization boundaries #176: merge base 50ac98cfa0ad9e8dd75f93ca437a5679fed4d804, feat(reference-host): add buyer integration safety fixtures #381 287 ahead / 86 behind;
• repository CI 32864768290: completed / failure for the packed Markdown RED above;
• Security Scan 32864768146: completed / success;
• SAST Semgrep 32864768158: completed / success;
• formal submitted reviews: 0;
• unresolved inline review threads: 0.

These mutable values are an operational snapshot only. Pending, queued, skipped-required, cancelled, absent, neutral, failed, stale, predecessor, status-only, model-only, wrong-checkout, synthetic-merge, or vacuous evidence is non-passing.

Reconciliation failure contract

The first causal product defect reproduced by #381 is already repaired at its owning #176 boundary. The remaining blocker is integration topology: both long-lived branches have diverged substantially and #381 also conflicts with current protected main. A stale GitHub synthetic merge tree from an earlier protected tip is not valid evidence for the current tip.

The presently exposed GitHub mutation surface has no safe high-level update-branch operation and no freshly resolved conflict-free merge tree for the current #381/#176/current-main combination. Therefore the exact source-reconciliation mutation is TOOL_UNAVAILABLE until a supported merge/update operation or trusted current merge tree is available. Do not emulate it by force-moving refs, destructive rebase, guessed tree construction, or copying the #176 fix into this competing writer. This classification applies only to that exact mutation; independent path-disjoint Inkspan work should continue.

Existing owner lanes, not duplicated here

• public Markdown adapter / serialization: Draft fix(reliability): harden public Markdown and local serialization boundaries #176;
• React test act(...) containment: Draft test(react): contain native reset updates inside act #153;
• large-document performance/support envelope: issue perf: define and enforce a large-document latency and memory support envelope #375 / Draft perf: add deterministic synthetic benchmark corpus #379;
• core forced-colors/focus/print source changes: canonical accessibility lanes fix(a11y): repair editor contrast and keyboard focus #362 and fix(accessibility): preserve forced-colors state cues #151;
• browser harness/input assurance: the existing dedicated browser lane, including test(input): add multilingual browser input baseline #380 where still live;
• release/publication/provenance: issue release: reconcile Office and npm versions before next stable registry publication #118;
• central dependency-review and exact-source scanner defects: their existing organization-owned paths, refetched live before reliance.

Remaining #377 acceptance

This PR remains partial buyer-journey evidence, not final #377 clean-checkout acceptance. After safe dependency/source reconciliation it must regenerate exact-current-head repository and central evidence and complete the supported reference application journey, including clean packed-artifact installation, SSR/hydration, native form, autosave success/conflict/ambiguous failure, host-owned collaboration lifecycle, read-only, stale proposal handling, browser/accessibility journeys, and deterministic Office/converter handoff.

Keep this PR Draft. Do not tag, release, mark Ready, merge, self-approve, transfer predecessor evidence, weaken gates, force-push/destructively rebase, bypass governance, or represent this Draft as integrated protected-main truth.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Current-head validation — 33c49bf

The packed Markdown boundary failure was caused by Turndown reading the ambient window property during module initialization. The Markdown build now probes a data-property descriptor instead, and Inkspan's browser fragment path uses the same fail-closed probe before touching document.

Validated locally at commit 33c49bf:

• CI=true vitest run src/referenceHostFrameworkFreePackedBoundary.test.ts — 1 file, 3 tests passed; packed ESM and CommonJS consumers import and execute under throwing window/document getters.
• CI=true vitest run src/markdown/serializer.test.ts src/markdownPackage.test.ts — 2 files, 45 tests passed.
• pnpm exec tsc --noEmit — passed.
• git diff --check — passed.

Hosted checks must be re-established for this exact HEAD; this comment is local validation evidence only.

[seonghobae]

Current-head OpenCode review request — 33c49bf

Please dispatch the authenticated OpenCode review for exact head 33c49bffd827ad3e2c8029d784ae7010a995a364. The required opencode-review check is correctly fail-closed because no qualifying opencode-agent APPROVED or CHANGES_REQUESTED review exists on this head. No readiness, approval, or merge claim is requested from this comment; the review must be posted by the configured authenticated reviewer.

[seonghobae]

Exact-head Strix evidence — 33c49bf

The canonical Strix job 98780208630 for exact head 33c49bffd827ad3e2c8029d784ae7010a995a364 completed with failure. The trusted scan materialized the PR-head scope (11 scannable files), but all three openai/orchestrator/free attempts returned HTTP 500 internal_error; no usable vulnerability report artifact was produced. The workflow therefore failed closed.

This is provider-side evidence, not a clean security verdict and not a merge waiver. The PR remains Draft and blocked pending an authoritative current-head Strix artifact and qualifying review.

[seonghobae]

Correction — current-head ownership reconciliation

The previous validation comment for 33c49bffd827ad3e2c8029d784ae7010a995a364 described a competing Markdown fix. That commit has been reverted normally at f6e1c60 because this PR's canonical ownership contract assigns the public Markdown/serialization boundary to Draft #176 and explicitly forbids duplicating that fix in #381.

Therefore the earlier 3/3 packed-boundary result is predecessor-only evidence and must not be transferred to the current head. Current #381 remains the original integration RED for the packed Markdown boundary, while #176 owns the existing repair. No force-push, destructive rebase, guessed tree, readiness, approval, or merge was performed. Supported source reconciliation remains unavailable under the documented branch-divergence constraint.