Abada 1.0.0-rc.2

Abada 1.0.0-rc.2 release notes

Abada 1.0.0-rc.2 is a corrective release candidate for the self-contained
Compose distribution. It preserves the PostgreSQL runtime, REST API v1,
external-worker protocol v1 and database schema from RC.1 while repairing the
first-run frontend experience.

This is published as a normal GitHub release, not a GitHub prerelease. The
rc.2 version still communicates product maturity: public-cloud production
certification remains deferred to the 1.1 infrastructure track.

Tenda diagram repair

Tenda now renders executable BPMN definitions that do not contain BPMN
Diagram Interchange coordinates. The viewer creates a temporary, vendor-neutral
layout model and reconstructs standard incoming/outgoing sequence-flow
references before generating shapes and connectors. The deployed definition
and engine execution semantics are not modified.

The release also removes the retired diagram-js keyboard binding and displays
an actionable error panel when malformed XML genuinely cannot be rendered.
The bundled approval workflow now includes explicit BPMN-DI coordinates.

The Tenda deployment client uses POST /api/v1/processes/deploy. The obsolete
/api/v1/processes/upload endpoint present in the original RC.1 image is not
used by the RC.2 bundle.

Platform onboarding

The Linux/macOS and PowerShell launchers finish with a structured success
panel containing URLs, health state, telemetry mode, starter identities,
first-run guidance, and exact log and teardown commands.

Development now includes separate starter identities:

Application	Username	Password
Tenda	alice	alice
Orun	orun-admin	orun-admin
Keycloak administration	admin	admin

If Keycloak reuses Alice's session when Orun opens, choose Sign out and
switch account and authenticate as orun-admin.

Service information contract

GET /api/v1/info now returns a typed service-discovery response containing
product and release identity, the documented BPMN support level, PostgreSQL
production persistence, API documentation links and authoritative health
probe links.

The earlier untyped status, profile, host/JVM runtime details and DMN/CMMN
roadmap claims are removed. Clients that treated this informational endpoint
as a health check must use the advertised Actuator liveness or readiness probe.

Image platforms

RC.2 is the first release built and verified for both linux/amd64 and
linux/arm64. The immutable RC.1 images remain amd64-only and continue to use
the launcher's explicit compatibility mode on ARM64 hosts.

Upgrade

No database migration is required between RC.1 and RC.2.

Download and verify the RC.2 bundle:

curl -fsSLO https://raw.githubusercontent.com/bashizip/abada-engine/main/release/quickstart.sh
chmod +x quickstart.sh
./quickstart.sh 1.0.0-rc.2

For an existing production-style installation, back up PostgreSQL, replace
ABADA_VERSION with 1.0.0-rc.2, run doctor prod, pull the images, and
recreate the application services. PostgreSQL volumes remain authoritative;
do not delete them during the upgrade.

Verification

The candidate is gated by the backend and frontend suites, dependency audits,
OpenAPI compatibility checks, the executable Compose deployment contract, the
checksummed release archive, and multi-architecture image-manifest validation.