GSM AI Agent Hub Pro 0.3.0-beta1.3.31

Release date: 2026-08-14

Previous version: 0.3.0-beta1.3.30

Release focus: Runtime consistency, Atlas observability, Visual worker recovery, strict final-visual gate.

1. Release/version consistency

• Package, component, system bridge and task plugin use one release version: 0.3.0-beta1.3.31.
• The package installer reconciles Joomla #__extensions.manifest_cache for all four installed extension records after upgrade.
• Newsroom, shared administration, module registry and the Guardian/License bridge read the current release instead of stale 1.3.29/1.3.30 literals.
• Existing legacy extension records are not blindly removed. The release only normalizes the active Agent-Hub package family.

2. Atlas Cloud agent assignments

• Managed KI-News agents are reconciled from the ambiguous Standard provider to explicit Atlas capability profiles.
• ki-news-bilderstellung / Mila König -> atlas-cloud-image -> bytedance/seedream-v5.0-pro/edit.
• Other managed KI-News agents -> atlas-cloud-text -> zai-org/glm-5.2 with task-based routing.
• OpenAI remains the route-level failover provider; administrators do not need to edit each bundled agent manually.

3. Atlas Billing & Usage normalization

• Billing endpoints are evaluated independently: Balance, Model Usage and Model Costs expose their own OK/HTTP/error status without leaking API keys.
• Atlas' inclusive start_date / exclusive end_date contract is normalized behind the UI field Bis einschließlich by sending the following UTC day as provider end_date.
• Daily usage buckets and nested results[] are flattened for the dashboard.
• Daily cost buckets and amount.value/currency are normalized for the dashboard.
• A missing balance permission no longer hides successful Usage/Costs calls.
• Internal provider-cost telemetry can be written even if customer-facing GSM Commerce/PAYG pricing rules are not configured; customer charge remains separate and zero until a valid server-side pricing rule applies.
• Every successful Atlas visual stores provider, model, prediction ID, latency, reference count, estimated provider cost and failover provenance.

4. Visual worker recovery

• A dedicated Joomla Scheduler task gsmagenthub.runtime_visual_1 is enabled at one-minute cadence, while the second visual lane remains disabled to avoid duplicate claims.
• Visual claim/retry remains atomic; stale visual leases are shortened so abandoned claims can recover faster.
• The central Alpha-6 watchdog remains the supervisory fallback.
• Workflow cancellation is wired to the real cancel_workflow server action and requires an audit reason. Running and queued jobs are cancelled revisionssicher.
• Neu laden produces visible workflow feedback instead of a silent click.

5. Final-visual publication gate

Full automation does not mean publishing a technically invalid visual.

• Release orchestration waits for a valid current style-anchor/composer proof.
• Channel preparation waits for the same proof.
• Facebook publishing waits for the same proof.
• Only an explicit audited administrator override may bypass this technical media gate.
• Publishing therefore cannot appear complete while the final visual is still invalid or merely queued.

6. Style anchor / Atlas visual quality controls

• The Atlas visual prompt explicitly rejects YouTube-thumbnail aesthetics, flat poster layouts, oversized red/yellow/black text panels, pseudo-text and decorative question-mark/warning graphics.
• The image model generates the editorial master motif; final typography, brand/logo, source badge and fixed editorial layers remain owned by the deterministic server composer.
• The current SHA-verified style anchor remains mandatory and can supply up to two additional validated reference images for Atlas multi-reference generation.
• Visual preview exposes provider/model/Atlas Prediction-ID and failover provenance so Atlas use can be proven rather than inferred from image quality.

7. AI_INCOMPLETE recovery

• Structured text/review calls detect AI_INCOMPLETE: max_output_tokens.
• The same provider is retried first with a larger output budget; only after that may the configured fallback provider be used.
• Fact-check, compliance, legal and editorial routes receive larger default output budgets.

8. Guardian installation-safe mode

• During verified nested Joomla package installation Guardian enters an installation-safe monitor window.
• The signed integrity core is not disabled and no blind restore is performed.
• The authoritative integrity scan runs after package installation and version reconciliation.
• This avoids a transient false manifest_signature_invalid event while files/manifests are legitimately being swapped.
• guardian.guardian_policy_scan_unavailable remains a separate MONITOR-only known issue and is not falsely marked resolved.

9. Standalone-first contracts retained

GSM Guardian and GSM Docs remain independently installable products. Agent-Hub integration is optional through adapters/connectors; neither product may depend on Agent-Hub tables or runtime for its core function. The existing GSM Docs release contract and all mandatory handoff documents are carried forward.

10. Agent model / voice configuration UX

• Agent settings no longer use a free-text-only model field. The model selector is populated from the selected provider; Atlas capability profiles can reuse the already refreshed Atlas master model catalog and filter it by Text/Image/Video/Audio capability.
• Managed KI-News agents are automatically reconciled to atlas-cloud-text or atlas-cloud-image; administrators no longer have to switch bundled agents from an ambiguous Standard setting manually.
• Changing the provider immediately refreshes the model dropdown and selects the provider default where appropriate, while a previously stored custom model remains visible as bisher.
• The previous voice UX is restored: selectable voice model, browser voice dropdown, speed/volume controls and a configurable probe sentence with Stimme testen.
• Voice preview is local/browser-side and therefore does not create provider cost. Server-side TTS remains configured independently through the stored Voice model.

Upgrade

Install directly over 0.3.0-beta1.3.30. Do not uninstall the existing package first. Existing provider credentials, project data, agent-authored prompts, style anchors, Telegram mappings and release history are preserved.