Changelog
What was built, in order
What was built and in what order, with what was left unfinished at each step.
Kept from the real work. It is not a list of announcements and it has no entries for things that did not happen.
-
The first real calls, through an actual carrier
Eleven calls through Twilio to a Romanian number, with real Anthropic, ElevenLabs and Sonix credentials. Five ended normally, six failed. The longest ran two minutes and six seconds and produced 232 events. Until that day no call had been through a real carrier.
-
A public site, in Romanian and English
Six sections and eight guides, written against the real console, with the same colours and the same components as the product. Including a page that says what has not been proven.
-
Build report
2,239 tests, of which 2,237 passed and 2 were skipped, each skip naming the credential it lacks. 171 tables, 305 REST routes, 221 paths in the OpenAPI document. The report states its own rule: nothing is claimed as working against a provider we have no credential for.
-
The interface fully translated into Romanian
Over five thousand keys per locale at exact parity, plus a field dictionary that translates form labels without touching the resources. Three automated tests guard the quality: comma-below diacritics, the informal register, and the three plural forms.
-
A FreeSWITCH switch and SIP scenarios
The switch boots clean from an empty volume with both SIP profiles running. Eleven of fourteen SIPp scenarios pass in a single run. The last two need a carrier gateway pointed back at the test harness.
-
A complete synthetic call through the real session code
The gateway drives a whole call against mock providers, including an interruption that runs all nine steps in order and discards the queued audio frames the caller must not hear.
-
Tenant isolation, fixed application-wide
The tests found a cross-organization read through implicit route-model binding: the middleware ran in the wrong order and a request for another organization resolved a real record before any policy. Fixed everywhere, with a regression test.
The dates are the ones in the build report and in this installation database.[1]
Notes
-
1
Sources:
BUILD_REPORT.md,TASKS.mdand thecalls/provider_credentialstables in the development installation.