Commits

Project activity for April 26, 2026:

agents.happitec.com

13 commits

• Implemented a full permission-prompt system across the UI and backend, including SwiftUI components, a PermissionPromptManager to handle state and lifecycle (with heartbeat watchdog and SSE reconnection logic for reliability), and integration into the scene root for system-wide accessibility.
• Connected the prompt UI across detail, list, and row views, enabling interactive prompt rendering and dispatch via a new permissionPromptReceived notification— wiring end-to-end from server event to user-facing interface.
• Protected Phase-2 prompt/rule operations with client-side wrappers, ensuring safe orchestration of prompt-related message handling and rule evaluation.
• Refined the Phase-2 plan by consolidating snapshot rules to merge-and-dedupe (per §7.2), updating UX placement guidance, and removing outdated Pushover/notify-prompt references, aligning the design with the latest feedback (#135).
• Added comprehensive test coverage for prompts—including manager logic, view-layer behavior, and mock fixtures aligned with actual operation IDs—ensuring correctness of the new prompt flow.

FederatedActivityPublisher

2 commits

• Improved DocC documentation routing and reliability: Added robustness to DocC’s path-based routing logic by addressing review feedback with 4 additional targeted test cases, ensuring correct URL mapping and fallback behavior for documentation pages.
• Optimized selective build performance: Fixed issue #223 by excluding DocC-generated files from the selective build process and switching to direct ZIP installation for the fast path—dramatically reducing build times and avoiding redundant processing of static documentation assets.

happitec-release-notes

6 commits

• Implemented Swift Package Manager (SPM) integration per docs/design-v1.md, establishing a modern, modular dependency management structure for the project.
• Refactored sheet presentation logic to use .sheet(item:), ensuring RecapScreen correctly receives and renders parsed release data—fixing prior issues with data flow and view state.
• Added XCUITest regression coverage specifically for sheet rendering to prevent UI regressions and validate the new sheet implementation.
• Incorporated Opus advisory feedback, including schema-level improvements (e.g., constraining the slug parameter) and architectural suggestions, aligning the design with production-grade validation and correctness principles.
• Proposed and formalized an initial design for happitec-release-notes, setting foundational direction for a dedicated release notes component or service.

ios-simulator-multitouch-mcp

2 commits

• Revealed new simulation logging controls by exposing sim_log_start and sim_log_stop MCP tools, enabling external systems to programmatically initiate and terminate simulation logging—a prerequisite for orchestrating repeatable test runs and capturing diagnostic telemetry in automated CI workflows.
• Audited and documented the MCP surface area, updating endpoint counts and linking to an open stale issue, which improves transparency of the API contract and helps prioritize future cleanup or deprecation work.

LetterSet

2 commits

• Claude Code Review automation enabled via CI configuration, allowing the happitec-computer bot to trigger AI-assisted code reviews, improving review consistency and reducing manual oversight.
• Hardware keyboard UX refinement by guarding SpacebarMoveView first-responder status behind hardware keyboard detection—preventing UI interference on touch devices where virtual keyboards are in use—ensuring a more predictable and platform-appropriate interaction model.

ota-app

3 commits

• Adopted happitec-release-notes as a Swift Package Manager dependency with bundled file support, enabling reliable access to release notes via a bundled resource path instead of external network calls or manual asset management.
• Fixed pinning and versioning issues by re-pinning and bumping the happitec-release-notes dependency to resolve a regression in .sheet(item:) presentation—ensuring compatibility with the latest SPM bundling mechanism and preventing runtime failures in the release notes view.

package-multitouch

1 commit

• Fixed broken documentation for the vm-daemon component by updating a stale DocC sub-link, ensuring developers can reliably access updated API reference material.

package-multitouch-vm

2 commits

• Package restructuring and documentation alignment: The package-multitouch-vm-client was introduced as a new, consolidated Swift package to unify the client-side multitouch and VM interaction logic, replacing fragmented or outdated module references; README and AGENTS.md were updated to correctly reference this new package, ensuring developers and automation tooling point to the canonical source.
• Documentation integrity fixes: A numerical drift (e.g., outdated version numbers or configuration values) in the VMDaemon DocC bundle—likely causing incorrect or misleading API documentation—was identified and corrected, restoring accuracy and reliability for consumers of the virtual machine daemon’s interface documentation.

package-multitouch-vm-client

12 commits

• Swift client and CLI tooling foundation: Introduced a Swift-based client library and executable (multitouch-playback) to enable programmatic and CLI-driven device interaction, establishing the core infrastructure for playback, testing, and remote control workflows (Phases 3.1–3.2).
• Playback command suite completion: Delivered a full CLI subcommand set for device playback operations, including status, replay, screenshot, simgesture tap+drag, start, and install+launch, collectively enabling end-to-end simulation and control of device behaviors (Phase 3.3).
• Improved reliability and testability: Added comprehensive library and CLI test coverage (Phase 3.4) to ensure correctness of playback logic and CLI interactions, alongside a fix to pre-process the OpenAPI spec to preserve /screenshot response bodies for Python clients—ensuring data integrity across language toolchains.
• Documentation rigor: Enhanced user-facing and contributor-facing docs (README, AGENTS.md) for the Swift client and CLI, and addressed reviewer feedback by clarifying non-exhaustive op listings—improving usability, discoverability, and maintainability.

package-paper-destruction

12 commits

• Migrated and modernized screenshot handling: Replaced the #70 workaround with a proper typed vm-client integration (v0.1.1), routing /screenshot through httpx, enabling type-safe, maintainable API interactions.
• Progressively refactored core infrastructure: Declared multitouch-vm-client as a dependency and migrated 10 JSON endpoints to use the new client library, laying the groundwork for a unified, typed interface.
• Implemented and validated canonical regression testing: Developed and executed a canonical variability regression plan and runner, added retry-on-divergence logic to stabilize tests, and uploaded results—now retroactively applied to post-migration validation in Phase 2.
• Improved clarity and maintainability of output: Renamed diff-pair columns to Δ(i,j) for mathematical clarity and merged multiple PR reviews to enforce YAML-driven scope definitions, 4% pass/fail thresholds, and taxonomy cleanup, aligning test configuration with explicit, auditable criteria.
• Documented engineering conventions: Added canonical-regression PR workflow to README and AGENTS.md, ensuring consistency and onboarding support for future contributors.