A dated record of material product changes since version 1.0.0. The notes describe shipped behavior, not a roadmap or a promise about an unpublished date.
Each entry groups changes that were completed on the stated date. Links lead to the current feature, whose documentation remains the source for daily use.
Supported changes moved into one guarded action catalog shared by the in-product assistant and external MCP connections.
A change is exposed only when the connected user’s role permits the underlying job.
Company settings choose between review proposals and immediate execution; destructive actions remain identifiable.
Every requested change creates a proposal record so authorship and outcome remain traceable.
Product modules were connected to the same permissioned vocabulary across the application and its external access paths.
Search and fetch return stable record identities with source links under the connected user’s permissions.
Document filing, daily-report records, working calendars and company-defined values were brought into the shared product model.
API, MCP and assistant access retain tenant and project boundaries instead of creating a second unscoped data path.
Core work screens were recomposed for phones and previously overloaded workforce and task pages were separated by job.
Navigation, actions, lists and detail screens were adjusted for narrow viewports and touch use.
Workforce functions moved to distinct pages so availability, shifts, time and qualifications no longer compete on one screen.
Relation fields became searchable and user invitations and task actions were made directly operable.
The application added machine-readable tenant archives, scheduled backups and a restore verification path alongside accessibility and tenant-isolation hardening.
Each tenant database can be exported table by table as NDJSON with row counts and SHA-256 checksums in a manifest.
Managed operation schedules nightly tenant backups and a weekly restore-and-compare verification.
Keyboard paths, screen-reader table context, focus appearance and translation parity were strengthened.
Version 1.0.0 connected the residential construction cycle from lead and estimate through field execution, purchasing, invoicing and warranty service.
Separate tenant databases, project-specific access and license and storage health checks formed the operating foundation.
Interactive schedules, supplier bidding, itemized progress billing, XRechnung, accounts payable and workforce costing were included.
Read/write API keys, rate limiting and signed asynchronous webhooks provided the first external integration layer.
The record makes product age and development activity visible. It can be checked against the current interface and documentation during a trial.
Release notes do not establish uptime, support response times or a future roadmap. Those commercial terms belong in the written agreement, while future work is only announced after it ships.
Request a trial and name the modules, interface and operating model your team needs to verify.
