Platform Updates

All six connected social destinations passed fresh hosted access verification. Bluesky public API discovery passes 27 checks without connecting a community account. Text delivery and cleanup are proven for Discord, Facebook and Telegram; the current audit preserves successful, failed and manually removed historical outcomes. The approved-media catalogue is empty, TikTok requires a genuine sandbox demo and production review, and X publishing remains blocked by its HTTP 402 billing response. No new live test post, test-media pack, AI image or paid credit purchase was made. The API acceptance ledger separates access, deployment and local certification from live media and provider recovery proof.

Social Publishing now applies the selected read-only support context to its administrative lifecycle and support-access routes. Current grants are checked against their operator, client and expiry/end state; support requests cannot change client status or create/end access grants. Normal administration and ending a session through its normal Admin action remain available. All 34 local publishing suites, API type-check and Worker build check passed. The Git-linked API release succeeded; authenticated checks from Admin confirmed readable support data, three blocked writes, ended-grant denial, unchanged client status and recorded start/end audit events. The temporary session was ended and no social posts were sent. Media, TikTok production review, X billing and real provider-recovery acceptance remain open.

Repository: FPH LAN EMS.

Operators receiving native packages now get versioned executable names with matching metadata and checksums. Release certification locates those exact packages rather than older unversioned names. macOS builds install the Go compiler required by the pinned LiveKit source; failed runs retain diagnostic reports. The current sign-in smoke check follows accessible field labels.

Validation: Local application checks, focused release-script type checking, two artifact-resolution tests and the release-workflow self-test pass. The first three-platform GitHub run exposed these packaging-workflow failures; corrected native certification and v0.1.1 publication are pending. This does not certify physical scanners or installed venue systems.

The macOS retry reached pinned LiveKit compilation and identified its native Darwin CPU statistics dependency. Source builds now default CGO on for macOS; the explicit compiler override remains available. Native certification continues on GitHub’s platform runners before any release tag is published.

LAN release integration also fixes bundled browser assets when the executable starts in a separate writable folder and completes incoming private-call controls, explicit camera publishing and push-to-talk cleanup. Current-source local validation passes managed LiveKit preflight, four API suites and six real React browser suites, including two-party video/audio and stopped capture on leave. Four focused release/asset-root tests and the release-workflow self-test pass. The v0.1.1 candidate passed native certification but remains an unpublished draft. The automatic intercom behavior supersedes it in the published v0.1.2 release. Physical devices and OS permission prompts remain unverified.