Skip to content

Update mobench.org for Mobench v0.1.45#8

Draft
dcbuild3r wants to merge 8 commits into
mainfrom
codex/mobench-v0.1.45
Draft

Update mobench.org for Mobench v0.1.45#8
dcbuild3r wants to merge 8 commits into
mainfrom
codex/mobench-v0.1.45

Conversation

@dcbuild3r

Copy link
Copy Markdown
Collaborator

Summary

  • rebuild the marketing and documentation surfaces around the pinned v0.1.45 release contract
  • document secretless preparation hooks, platform-specific function/device matrices, and fail-closed complete-result enforcement
  • regenerate CLI/config references, manifests, LLM indexes, OG images, and reviewed visual baselines

Release evidence

  • upstream tag commit: 434da93dfda39db996be90e9e0bca625f10efb25
  • reusable workflow pin: 3dc3d5be6add73a1b2f6c3edefb862fd485356c2
  • release assets omitted the website manifest/checksum, so the truth package is explicitly marked offline-tag-verified and records its local checksum provenance
  • cargo mobench remains unsupported; examples retain the canonical mobench executable

Verification

  • bun run check
  • bun run test (12 passed)
  • bun run test:e2e (9 passed)
  • bun run test:lighthouse (marketing and docs assertions passed)
  • git diff --check

Draft until the Vercel preview has been reviewed and production promotion is explicitly approved.

@vercel

vercel Bot commented Jul 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
mobench-org Error Error Jul 18, 2026 2:02pm
mobench.org Error Error Jul 18, 2026 2:02pm

@dcbuild3r

Copy link
Copy Markdown
Collaborator Author

Vercel preview

The Git-integrated projects still use the legacy root dist assumption, so I published verified app-scoped prebuilt previews for this PR commit (845aa81):

Both deployments are READY and returned HTTP 200 through their temporary 23-hour share links. Marketing contains the v0.1.45 release block; docs contain prepare_script, functions_ios, android_devices, and complete-shard enforcement. Production has not been changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant