Agents.Grishen adoption of AgentPlat 1.4.0

This is a dated integration record for 2026-10-23, not a claim about the application's current configuration or a qualification of every AgentPlat capability. Package publication and application deployment were separate steps.

Delivered and checked

The coordinated dependency closure was pinned to published AgentPlat 1.4.0, including Planner, workflows and artifacts. Registry verification checked the 27 resolved AgentPlat packages against their locked distribution archives. The deployment workflow (opens in a new tab) completed successfully for commit 352e06db2b72d12bdca86d7c77206930413e2f61.

During the owner-authorized maintenance window, the old application was stopped before applying Rooms 019, workflows 001 and artifacts 001–002. The artifact namespace was separate from Rooms. All three ledgers reported their expected versions with no pending migrations. Existing Room and message counts were unchanged by the migration. The updated single application task and its Local Node were restored; health reported AgentPlat 1.4.0 and the authenticated UI loaded existing Room history.

A manual artifact check in an existing test Room created an artifact, saved its second revision and read the first revision with editing disabled for that historical version. This check used no model call. CI additionally covered artifact authorization, revision conflicts, HTML preview boundaries, a synthetic old-schema upgrade, durable Planner recovery, build and Node 22 standalone startup. Those checks do not establish general production-scale reliability.

Activation boundary at deployment

Planner code and database support were deployed, but Planner remained globally disabled. Model prices, an owner-approved persistent Room budget and a bounded observation pilot were still required before execution. Installed capability is not an active autonomous workload.

Artifact tools require explicit per-agent grants and current Room membership. The app supplies verified identity, API authorization, content limits and a sanitized sandboxed HTML preview. At this deployment the UI refreshed durable artifact heads; no artifact event dispatcher was registered. Applying the outbox migration did not enable push delivery.

Temporary migration compute, IAM permissions, network ingress, storage and maintenance flags were removed after the upgrade. Recovery after Rooms 019 must use a compatible image; an old adapter is not a safe automatic rollback target.

See the Planner activation guide, artifact integration guide and coordinated migration procedure.