[GP1-S1] Runtime WAL Store Adapter Boundary

[flyingrobots]

Roadmap slice: GP1-S1
Goalpost: Goalpost 1: Durable Runtime WAL Join
Parent: #521
Related: #510, #518

Source: docs/design/wal-wsc-durability-roadmap.md on branch cycle/521-wal-wsc-storage-relationship at bde7957c.

Scope

Parent issues:
#510,
#518,
#521.

Scope:

• Introduce a trusted-host-owned runtime WAL adapter boundary over
  WalStorePort.
• Keep application APIs limited to submission handles and outcome observation.
• Preserve the existing in-memory runtime WAL adapter for fast tests.

Acceptance:

• TrustedRuntimeHost owns the adapter configuration.
• TrustedRuntimeApp exposes no WAL append, flush, truncate, manifest, tick,
  or recovery method.
• Existing runtime WAL ACK tests still pass through the adapter boundary.

Witness:

cargo test -p warp-core --features "native_rule_bootstrap trusted_runtime host_test" --test trusted_runtime_host_loop_tests runtime_wal_ack

Dedupe note

This is the PR-sized implementation slice for the roadmap item above. Existing umbrella or adjacent issues remain linked as Parent/Related rather than duplicated here.

[coderabbitai]

🔗 Related PRs

#323 - Witnessed suffix admission evaluator [merged]
#360 - feat(core): stage ticketed ingress and outcome observation [merged]
#368 - feat(core): connect installed contract intent pipeline [merged]
#379 - feat(core): commit runtime WAL ACK evidence [merged]
#550 - Expose braid membership history [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!