v3.220.0 · Hub inbox persistence live verification

Hub Inbox Live Verification Closure

Human reviewers can close live evidence gaps for the hub inbox without allowing client acknowledgements, status replies, no-op talk-back, reviewer exports, ErrorNotifier signals, or CreativeExpansion proposals to become protected-anchor apply events.

Receipt ≠ approvalAcknowledgement ≠ executionExport ≠ applyTelemetry ≠ remediation

Live verification closure

Blank human-fillable fields cover admin table state, read-only route status, OpenAPI parity, static JSON mirrors, cache state, screenshots, reviewer identity, and UTC review time.

Apply-boundary red team

Fixtures attempt to transform acknowledgement, status, talk-back, reviewer export, CreativeExpansion proposal, and ErrorNotifier signal into anchor apply. Every expected outcome is reject, quarantine, no-op, or review.

Reviewer workflow pack

Exports contain screenshots, JSON parse output, route status, cache state, OpenAPI checks, and human notes. They remain evidence, not active system mutation.

Closure targets

Hub inbox tables

Verify `hub_inbox_rows`, `outbound_instructions`, `acknowledgement_receipts`, and `reviewer_evidence_exports` after deployment.

REST route

Verify `/wp-json/uaix-talisman/v1/teleodynamic/hub-inbox-live-verification-closure` returns readable JSON.

OpenAPI parity

Confirm `getTeleodynamicHubInboxLiveVerificationClosure` appears and dangerous operations remain omitted.

Root-static discovery

Verify `/llms.txt`, `/ai-router.json`, `/.well-known/ai-agent.json`, and `/sitemap.xml` advertise the current safe read order.

Machine-readable files