Key points
- The team updated the automerge gate to use the server clock for accurate timing.
- The dispatcher now accepts multiple matching verdicts and pages through review reads.
- The phone system enforces plan limits gracefully with a grace period for outages.
- Security measures now require positive human evidence for approving non-agent credentials.
The automerge system stopped trusting committer dates and started listening to the server’s clock. For weeks, the gate that decides whether to send a pull request back for review relied on the timestamp attached to the commit object. That works fine when the world is simple, but it breaks down when a PR is force-pushed or when a repository’s history gets rewritten. The dispatcher now calculates push time as the earliest of the timeline entry and the status creation, ensuring that a PR sent back for changes actually waits for the review to land, rather than racing ahead on an old timestamp. This keeps the merge queue honest.
The agent-dispatch repo saw twelve commits to tighten this logic. The dispatcher now accepts reports where all VERDICT lines agree, dropping the previous restriction that rejected duplicate verdicts. It also pages through review reads so that a second page of REQUEST_CHANGES does not slip past the gate. The User-Agent string on urllib requests is now named, which helps with debugging and monitoring. Tests were updated to replay fixture stamps per-sha statuses, and legacy automerge fakes were given the timeline GET endpoint they need. The push time gate now matches the real Forgejo timeline shape.
On the product side, the phone system learned to enforce plan limits with more grace. When a paid plan ends, the account moves to free limits immediately. The system keeps the last verified plan for up to twenty-four hours if the Ops-Center is unreachable, preventing a sudden lockout during network hiccups. This LAST_VERIFIED_PLAN_GRACE period is now backed by tests that verify the transition from paid to free, and the handling of unreachable or error responses. Meetings under legal hold can no longer be manually deleted, protecting evidence integrity. The auto-summary socket now skips server summarization for organizations that do not have server text storage enabled, avoiding unnecessary work.
The auto-summary socket now skips server summarization for organizations that do not have server text storage enabled, avoiding unnecessary work.
Security tightened around the agent inbox and MCP tools. Approving or rejecting non-agent credentials now requires positive human evidence, closing a gap where automated or partial credentials could trigger actions without clear human intent. The REST endpoints for the agent inbox now require the agent-inbox:approve scope on a personal access token, ensuring that only authorized tokens can bulk approve or reject messages. SSO link merges no longer reinstate access that an operator has explicitly removed, and collisions in the restrictive direction are resolved correctly.
The contact picker in the customer dashboard received a clearer message when a workspace is not connected to Contact-Ops. Instead of showing a picker that cannot function, it now displays a specific instruction to connect Contact-Ops first. Creating a relationship returns a 409 status when the workspace lacks a Contact-Ops mapping, with cross-org isolation tests verifying the boundary.
Provisioning operations locked down admin rows before counting members, and user delete operations now commit the lock, count, delete, and audit log action together in a single transaction. Profile downloads in calendar-ops use a dav-auth lock order with a per-source limiter to prevent resource exhaustion.
The day was busy with refinements. The automerge gate is now time-accurate, plan limits are resilient, and review gates are tighter.
- ops-center89
- unicorn-stable64
- contact-ops46
- agent-dispatch40
- uc-meeting-ops36
- customer-ops25
- unicorn-brigade20
- email-ops7
- 5 other repositories11