APEX 1.0.1

APEX 1.0.1

This release brings the integrated factory showcase to the MCP App: MES and saved Excel data can be imported, planned, independently validated and explored through a branded Planning overview in chat.

Product changes

• Add an optional demo adapter for the public MES API and saved Excel workbook. It exports canonical scheduling facts and source evidence, detects newly added rows, preserves explicit commitments, and rejects malformed or ambiguous data with source locations.
• Ship the standard Planning overview with aggregate KPIs, delivery outcomes, critical orders, resource utilization, work mix and searchable schedule navigation. Package hooks support additional views and renderers; the demo supplies MES/Excel source coverage and import notices.
• Correct general construction to consider machines, phase-specific staff, shifts and material when selecting feasible modes. Construction and full decoding share transactional placement state for eligible models; neighbor-dependent and native-policy models retain their full decoding path. Dated stock reservations allow independent earlier work without borrowing future material.
• Keep the application, engine, middleware and desktop package versions aligned so MCP discovery and result provenance identify the same product release.
• Provide the central control platform with authenticated HTTP/MCP access, scenarios and immutable revisions, background planning runs, saved results and PostgreSQL persistence. Runtime configuration selects optional packages; the standalone application remains independent of contributor tooling.
• Include standalone and composed demo container deployment, a bilingual synthetic MES, the shared saved workbook and local onboarding with resume/reset and connection details. Explicit adapter import leaves MES and workbook records unchanged.
• Improve input diagnostics for zero processing allowances and Excel proposals beyond the selected horizon. Keep source-specific interpretation in customization modules and reusable planning/display behavior in the application.

Verified showcase and limits

The complete synthetic source contains 3,800 MES operations and 3,800 Excel rows. Excluding completed history leaves 3,705 operations, including six running operations and 65 locks. With the horizon explicitly extended to October 30, 2026, the existing release strategy constructs a complete independently validated plan without replaying Excel assignments or ordering. A local Windows release-build measurement took about 2.3 seconds. The resulting plan has 41 of 118 remaining orders on time; this is a feasible starting plan, not an optimization or delivery-performance claim.

The original October 16 source horizon and the default queues strategy did not yield complete plans in these checks. Failed greedy construction does not prove infeasibility. Horizons are never extended automatically. New source edits require a fresh import, planning run and validation. The adapter guide describes the explicit tested showcase settings.

Validation

Local checks passed Rust formatting, Clippy with warnings denied, 173 Rust tests (two explicitly ignored), 22 adapter tests with the release engine, 54 contributor tests and 54 MES tests. The standalone source export builds and exercises all five planning methods and additional fixtures. A clean source publication scan, documentation/wiki checks and both language-template checks passed.

MCP SDK, control-platform and browser checks cover branding, charts, filters, custom views, revision pinning, validation state, errors, schedule search and responsive layouts. The full factory result renders all 3,705 operations with a bounded initial schedule view. Isolated standalone/demo container checks exercise authenticated planning, the full MES/Excel import, MCP views, database isolation, restart persistence and reset behavior.

Contributor maintenance

Reconcile onboarding with the implemented adapter, publish the Planning overview guide in the wiki, mark superseded implementation plans as historical and keep architecture/search documentation aligned with shared placement and dated material reservations. Runtime snapshots, generated reports and local credentials remain outside the source distribution. Required benchmark and migration evidence is retained.