Project activity for July 06, 2026:
agents.happitec.com
7 commits
- Redesigned the Important-tier notification system with a new app-side plan (superseding #458), refocusing UI and logic for improved user prioritization.
- Enhanced keyboard accessibility across macOS/iOS, adding: navigation into collapsed groups with scroll-to-agent visibility (#449), explicit mapping of
AgentKeyboardOrderto sidebar order (not screen visibility), and new global shortcuts (⌘0,⌘⇧I,⌘Shift+[ / ]) for rapid sidebar/inspector/grouped-agent workflow. - Updated OpenAPI spec integration to align client with backend API changes, ensuring typed consistency across platforms.
- Executed two releases (1.8.0 → 1.9.0) reflecting incremental stability improvements and new input navigation features across iOS/macOS (builds 306/217 → 307/218).
dash-agent
13 commits
- Refined “important” tier architecture: Introduced a new
stop-eventsignal type and associated ingest, guard-correlate-emit pipeline for reliable critical-state handling across agents, with per-agent debounce (defaulting to 180s post-cadence call) to prevent storming during coordinator transitions. - Reliable lifecycle termination: Implemented a synchronous, feed-only
/stopendpoint and integrated it into the dash-agent’s end-of-sequence flow via a dedicated stop hook, ensuring clean shutdown without missed events or duplicate signals. - Push-proxy enrichment: Extended push-proxy to natively support non-prompt “important” kind messages (including
stop-event) with deduplication bydedup_id, improving idempotency and reducing redundant alerting in downstream systems. - Spec & integration alignment: Finalized §7 open questions, advisory review findings, and administrative gates per Erin’s rulings—consolidating design decisions into the spec (e.g., folding thinker-independent and advisory reviews), and documenting
POST /internal/stop-eventto clarify hooks → push-proxy → ingestion flow.
ota-app
1 commit
- Fixed a critical UI stuck-state bug in the build comparison feature where the “own-row” view would indefinitely display “Update” due to failing to account for server-side sub-counts during status evaluation, ensuring accurate sync state indicators.
- Improved synchronization reliability by adjusting how row-level build statuses are computed against upstream server data, resolving a long-standing edge case where client-side counts diverged from the server’s authoritative counts.
package-multitouch-tester
1 commit
- Implemented a new recorder pin configuration system that single-sources the pin assignment from a JSON definition file and uses compile-time code generation (via
codegen) to eliminate runtime overhead and human error—ensuring consistency across firmware, simulation, and hardware test benches. - This change decouples hardware abstraction from implementation logic, enabling rapid iteration on pin mappings without touching C++ source, while strongly typing the resulting API to prevent misconfigurations at compile time.
push-proxy-impl
1 commit
- Introduced a new
importantnotification kind to elevate critical system alerts (e.g., data integrity issues, service outages), enabling distinct routing and handling logic separate from standard or low-priority notifications. - This change enhances the agent’s operational visibility by ensuring high-severity events receive priority treatment in downstream alerting and observability pipelines—reducing response latency for incidents requiring immediate attention.
shpool-resume
1 commit
- Refactored session routing logic in
sessions.jsonto explicitly routepush-proxytraffic through thepubsubhandler, aligning with Erin’s operational ruling and ensuring compliance with the external-firewall policy for the AWS deployment lane. - This change enforces a security boundary, clarifying that all push notification infrastructure (via
push-proxy) must transit through the centralized pub/sub layer—preventing direct or unauthenticated connections—and strengthening observability and access control for real-time messaging in the cloud environment.