Sentinel Signal

MCP Verify 1.0.630 deployment verification

Source: docs/mcp-verify-v1.0.630-deployment-verification.md

Document Content

MCP Verify 1.0.630 deployment verification

Date: 2026-08-14

Release identity

  • Release version: 1.0.630
  • Release commit: 4762ff9e3f9f1ce3a785d7895b4fc5cd7aff40be
  • Deployed build SHA: 4762ff9e3f9f1ce3a785d7895b4fc5cd7aff40be
  • Production target: IONOS /opt/sentinel-signal
  • Cache invalidation: complete Verify service restart at approximately 2026-08-14T03:48:51Z

Predeployment gates

  • Verify test suite: 812 passed
  • Root unit suite: 194 passed, 115 deselected
  • make test-suites: 309 passed; 75.71% line and 60.85% branch coverage
  • Predeployment invariants: all 29 checks passed
  • Working-tree and release-version check: clean release commit; package and runtime version 1.0.630

Trust-summary checks

Record the canonical and cache-busted first-cold and warmed requests. Each must show partial=false, no unavailable fields, no cache note, complete materialization, request-current generation/evaluation timestamps, no-store browser/CDN/surrogate headers, and the same current evidence snapshot.

| Request | Snapshot | Generated at | Trust evaluated at | Materialization | Cache state | Result | |---|---|---|---|---|---|---| | Canonical, first after revalidation | trustsnap_77736105292f62fa | 03:55:17.989779Z | 03:55:17.989779Z | complete | miss_refresh | passed | | Query variant, first after revalidation | trustsnap_77736105292f62fa | 03:55:26.617661Z | 03:55:26.617661Z | complete | hit | passed | | Canonical, warm | trustsnap_77736105292f62fa | 03:57:01.533546Z | 03:57:01.533546Z | complete | hit | passed | | Query variant, warm | trustsnap_77736105292f62fa | 03:57:01.735389Z | 03:57:01.735389Z | complete | hit | passed |

Tracepass checks

  • New validation ID: cd10df0d-db8d-43e6-9d04-fc0e60e956bf, completed 2026-08-14T03:51:40.512419Z
  • Instruction references: archive_passport, suspend_passport
  • Missing instruction tools: archive_passport, suspend_passport
  • Instruction remediation row count: one (fix_instruction_tool_references); duplicate alert-response row absent
  • Placeholder remediation actions: none for connector publishability, official registry publication, or card-schema omission; all three carry concrete actions and three-step playbooks
  • Cross-surface coherence synthetic: two post-validation iterations passed on trustsnap_77736105292f62fa
  • Recurring coherence timer: active/waiting; manual service run 03:55:58Z–03:56:32Z, Result=success, ExecMainStatus=0; next run scheduled 04:01:25Z

Raw operational evidence

/version returned version/package 1.0.630, build SHA 4762ff9e3f9f1ce3a785d7895b4fc5cd7aff40be, trust-core-v2, the canonical 20-run/2-full-payload history, final detail HTML caching disabled, and a 60-second route-cache stale limit.

The independent canonical and query-variant responses both returned:

HTTP 200
partial: false
fields_unavailable: []
cache_note: absent
materialization.state: complete
materialization.trust_core_complete: true
cache-control: no-store, max-age=0, must-revalidate, no-transform
cdn-cache-control: no-store
surrogate-control: no-store
x-mcp-verify-materialization-state: complete
x-mcp-verify-version: 1.0.630

Both reported confidence 100.0 with an explicit basis of 20 evidence-bearing validations, 22 affirmative checks, and a 24-hour freshness threshold. Both reported two low alerts and zero high/critical alerts. Generation and trust-evaluation timestamps advanced on every canonical and query-variant response while the evidence-lineage snapshot remained stable.

The deployment synthetic first passed twice on the pre-revalidation snapshot trustsnap_9328fa0faf5f068a. The accepted revalidation rotated every surface to trustsnap_77736105292f62fa. A subsequent systemd synthetic again passed twice with complete trust-summary materialization, empty omissions, no-store headers, and advancing timestamps.

Status: passed