v0.5.7

Full Changelog: v0.5.6...v0.5.7

v0.5.6

Full Changelog: v0.5.5...v0.5.6

v0.5.5

Full Changelog: v0.5.4...v0.5.5

v0.5.4

Full Changelog: v0.5.3...v0.5.4

v0.5.3

Full Changelog: v0.5.2...v0.5.3

v0.5.2

Supersedes v0.5.1 after fixing dev startup blockers and stabilizing full frontend release validation.\n\nValidated on the dev EC2 checkout at commit ea3b282 with backend unit, contract, integration, and frontend test/build checks passing legitimately.

v0.5.1

Patch release that supersedes the earlier v0.5.0 candidate after replacing skip-based test shortcuts with legitimate runtime and test fixes.

Full Changelog: v0.5.0...v0.5.1

v0.4.0

v0.4.0 — Standalone Docker Installer & Modular Packages

Highlights

This release introduces Docker-based standalone deployment with a guided interactive installer, a modular package architecture for extensible agent and tool catalogs, and numerous reliability improvements for independent installations outside Alliance infrastructure.

Docker-Based Standalone Installer

A new 6-stage interactive installer walks through a complete standalone deployment from scratch:

• Preflight validation (Docker, disk space, ports, required tools)
• Environment setup with secrets generation and published image resolution
• Authentication configuration (OIDC or dev mode)
• User group setup (custom group names, species, provider mapping)
• PDF extraction service setup (clone, configure, GPU detection)
• Docker Compose stack startup and health verification
• Resume from any stage, pin to a specific release version
• Auto-detection of CPU/RAM for PDF extraction worker limits
• GPU detection for Docling and Marker extractors
• Progress breadcrumbs and clear failure guidance at each stage

Modular Package Architecture

The backend runtime is now organized into installable packages with isolated Python environments:

• Alliance Core (agr.core): Minimal runtime with supervisor chat, task input, and base tools
• Alliance Defaults (agr.alliance): Full AGR/Alliance specialist and tool catalog
• Package profiles during install: core only (default) or core + alliance
• Add the alliance package later without reinstalling
• Package discovery, validation, health reporting, and per-package Python environments
• Tool resolution and Agent Studio catalog are now package-aware
• Migration helper for existing repo-based installs

Published Docker Images

Three runtime images are published to AWS ECR Public for each release:

• Backend, frontend, and trace review backend images
• Release assets include bundled package tarballs, a pinned environment template, and a machine-readable release manifest

Core-Only Install Improvements

• Backend starts cleanly with only the core package installed
• Supervisor chat works without alliance specialists
• Agent Studio helpers degrade gracefully without the alliance package
• Connections health no longer degrades for unconfigured optional services
• Chat UI suppresses warnings for services that are not configured
• Config seeding no longer crashes on core-only installs

PDF Extraction Service

• Health check now correctly recognizes healthy extraction services on standalone installs
• Errors only surface when the service is actually degraded, not when optional endpoints are missing
• Installer writes Docker-compatible URLs so the backend container can reach host-local services
• Deployment docs updated with PDF extraction networking guidance

Frontend Fixes

• Fixed blank white page caused by cyclic chunk splitting in production builds
• Fixed auth/login redirect loop caused by missing proxy rules for API routes

Other Changes

• Renamed MOD terminology to Group across the entire platform
• PDF chunk highlight tracking fixes
• Upload runtime contracts and orchestration refactored
• Flow results injected into chat context for follow-up questions
• Removed hardcoded model version references
• Installer and publish-artifact regression suites now run in CI
• Docker build cache scoped per image to prevent cross-contamination
• Trace review backend published as a standalone image

Full Changelog: v0.3.4.2...v0.4.0

v0.3.4.2 — Weaviate hardening + startup safety

Changes since v0.3.4

Weaviate Infrastructure Hardening

• Pin Weaviate to cr.weaviate.io/semitechnologies/weaviate:1.33.18 (was latest from Docker Hub)
• Disable auto-schema (AUTOSCHEMA_ENABLED: "false") to prevent ghost collections
• Enable backup-filesystem module with ./weaviate_backups volume mount

Startup Safety Fix

• Remove destructive Weaviate collection migration from startup — the previous code silently deleted and recreated Weaviate collections (destroying all data) if they lacked multi-tenancy. Now the backend refuses to start with a clear error directing operators to run a manual migration script instead. Weaviate schema changes should not be handled by automatic startup logic.

Full v0.3.4 changes included

• ALL-6: Drag-and-drop PDF upload in viewer panel
• Snackbar notification when PDF background processing starts
• ALL-9: Update GPT model references from gpt-5.2 to gpt-5.4
• Version bump, changelog, and workspace improvements

v0.3.4.1 — Weaviate Hardening Hotfix

Hotfix: Weaviate Configuration Hardening

Patches v0.3.4 with critical Weaviate stability fixes discovered during dev testing.

Changes

• Pin Weaviate version to 1.33.18 from official registry (cr.weaviate.io) — was using latest from Docker Hub
• Disable auto-schema (AUTOSCHEMA_ENABLED=false) — prevents ghost collections from being created without multi-tenancy when real collections are lost
• Enable backup-filesystem module — adds native Weaviate backup API support (/v1/backups/filesystem) with ./weaviate_backups/ host volume mount

Context

During v0.3.4 dev deployment, Weaviate collections were mysteriously deleted. Auto-schema then recreated PDFDocument without multi-tenancy, causing PDF upload failures (422: "class PDFDocument has multi-tenancy disabled, but request was with tenant"). These fixes prevent recurrence.