Waypoint 1.1.0 — IPM installation

Waypoint 1.1.0 adds IPM installation of the production frontend, bundled gateway dependencies and native extension. Node.js 22.12+ remains required; no npm or compiler is needed on the target host. Follow docs/WAYPOINT_IPM.md for installation, service setup and lifecycle operations.

The launcher requires explicit origin, cookie, instance and external data settings. It rejects relative or package-contained data locations, including symlinks. The extension installer refuses a route owned by another dispatch class or namespace. It creates no native accounts, credentials, grants or sample tasks. Package resources have application-specific names.

Validation: production build and 257 source tests plus two packaging tests. Isolated IRIS 2026.2/IPM 0.10.8 source and archive installations, native login and extension reads, retained records after uninstall/reinstall, conflicting-route refusal, desktop and 390px browser checks passed. External records remained byte-identical. Existing production data and earlier releases are unchanged.

IPM publication is requested through the existing Open Exchange application. Registry availability and bonus awards are separate from local package validation.

Waypoint 1.0.19

Run creation now distinguishes 100 unarchived runs from 1,000 total records. Both built-in plans and saved procedures explain when archiving can help and when it cannot. Limits, stored data and restoration obligations are unchanged.

Validation: production build and 257 tests passed, including both capacity boundaries and rejection without native calls or writes. The actual frontend was checked at desktop and 390px widths with synthetic storage and the real creation guard.

Waypoint 1.0.18

Run comparisons now retain the collection context of both observations. A record present in only one bounded response is labelled Only in before or Only in after, with an explicit warning that this does not prove native creation or deletion.

Comparison JSON preserves recorded request limits and legacy notices. A summary warning remains visible when unchanged sources are hidden. Existing identity matching, field differences, comparison limits and saved run records are unchanged; request limits are not treated as proof of truncation.

Rebuild only the portal service and retain the configured instance ID and run-data volume. No migration is required.

Validation: production build, 255 tests and nine actual-component browser checks pass. Desktop and 390px checks cover shifted windows, legacy limits, unchanged-source filtering and keyboard table scrolling. Synthetic data only; no native calls or existing records were changed.

Waypoint 1.0.17

Successful inventory and task-history observations now retain the row limit used in the request. The run view, JSON handover and printable report expose that limit so a bounded result is not mistaken for a complete inventory.

The limit is recorded with new successful reads. The run view and printable report identify older observations whose collection limit was not recorded; no historical value is inferred. The evidence payload, assertion paths, native requests and execution authority are unchanged. Logs retain their existing source-specific limits.

Rebuild only the portal service and preserve the configured instance ID and run-data volume. Existing run records remain readable without migration.

Validation: production build, 251 tests and 8 actual-component browser checks pass. Memory-only engine tests verify the exact request parameters, unchanged evidence, legacy validation and failed retries. Desktop and 390px checks verify the current and legacy notices and the generated HTML. No native calls or existing run records were changed.

Waypoint 1.0.16

When the response to creating a run from a saved procedure is lost or unreadable, Waypoint now marks the outcome unconfirmed and blocks an immediate duplicate attempt. Check recent saved runs, open the relevant record and inspect its procedure version before deciding whether to create another plan. An empty list is not proof that creation failed.

Definite refusals remain retryable. Creating a plan does not execute any step. Existing run formats, procedure versions and native permissions are unchanged. Rebuild only the portal service while preserving its configured instance ID and existing data volume.

Validation: build and 247 tests pass, plus 18 actual-component browser checks. Desktop and 390px manual checks covered lost responses, recovery reads, inline history failures, explicit acknowledgement and saved procedure identity. Synthetic fixtures made no native or durable writes. The guard lasts while the page remains open; after a full reload, inspect Runbooks before repeating an interrupted creation.

Waypoint 1.0.15

Printable handovers identify the observation behind each procedure assertion by step number, title and identifier, with its source and target. This makes a failed or unknown check traceable when several observation steps share a title. Missing references are reported explicitly rather than inferred from names.

Recorded outcomes, procedure versions and saved runs are unchanged. The report does not rerun checks. Rebuild only the portal service, preserving the configured instance ID and existing data volumes. No native class or stored-data migration is required.

Validation: production build and 247 tests pass, including eight report tests for exact references, pending and unknown checks, missing sources, escaping and legacy output. Manual desktop and 390px inspection of the generated report confirms the referenced step and target are readable without page overflow. Synthetic data only; no native or durable writes.

Waypoint 1.0.14

Procedure import errors now identify the field that needs correction, including nested checklist items and references. The pasted JSON stays available for editing after validation fails. Unknown fields and unsafe references remain rejected; valid definitions retain their existing IDs and values.

The workflow guide explains how to locate an entry from its JSON path. This update changes error reporting only; it does not change the import format, validation rules or stored procedures.

Rebuild only the portal service while preserving the configured instance ID and existing data volumes.

Validation: production build and 243 tests pass, plus eight actual-component browser checks and manual desktop/390px checks. Synthetic records only, without IRIS or durable writes.

Waypoint 1.0.13

Version comparison now includes the definitions of added and removed procedure steps: observation sources and targets, instructions, checklist items and references, and assertion dependencies and expected results. The same details are retained in the JSON comparison export.

Recreated steps remain separate additions and removals, matched by stored identifiers. Existing runs retain their original procedure version. This update does not change execution, saved procedure data or native permissions.

Rebuild only the portal service while preserving its configured instance ID and data volumes.

Validation: production build and 241 tests pass, plus ten actual-component browser checks of displayed definitions, exported JSON, reverse and identical comparisons, and literal text rendering.

Manual desktop and 390px checks confirm readable definitions and wrapped long targets without document overflow. Test data was synthetic; no native or saved records were changed.

Waypoint 1.0.12

Command results in task actions and the Command station now retain the sent command ID when receipt access fails, while hiding previously downloaded evidence. Retry receipt access reads the saved ID without executing the command or repeating reconciliation. A refused or missing reconciliation response triggers a separate read-access check; an allowed read restores current evidence.

A recovered record that still contains its pre-execution review is labelled Execution outcome unconfirmed. It cannot reopen Execute once. A conflict found before dispatch still preserves the draft because no command was sent. Recovery moves keyboard focus to the notice and then the restored result; late responses from a closed workspace are ignored.

The workflow guide describes recovery, and the README distinguishes typed confirmation for deletion/native actions from the explicit execution button for other reviewed updates.

Rebuild only the portal service, preserving the existing instance ID and data volumes. No native class or data migration is required. This improves handling of cached evidence; server authorization remains in place and previously exported files cannot be revoked.

Validation: production build, 236 Node tests and 41 actual-component browser checks passed. Manual desktop and 390px checks covered denied/transient access, keyboard recovery, retained command identity and an unconfirmed result without an execution button. Synthetic transport only; no native or durable writes.

Waypoint 1.0.11

Command history now checks saved-record access separately after a refused or missing reconciliation. While checking, it hides the matching result and filtered-index export entry. A successful GET restores the current record; a missing or forbidden record is removed. Temporary failures offer Retry record access without repeating the original command or its reconciliation.

Older refresh responses no longer replace a more recently selected command. Search, outcome and date filters are preserved, and recovery moves keyboard focus to the relevant message or restored result. A failed index read does not prevent an independent, authorized detail read. A temporary read failure for the same selected record retains its previously read evidence.

The documented Node.js requirement is now 22.12 or newer, matching the existing build tools. No dependency upgrade is included. Rebuild only the portal service and preserve the configured instance ID and data volumes; no native class or data migration is needed.

History filters now fit their desktop panel, and the Reviewed command fields table supports keyboard scrolling on narrow screens.

Validation: production build, 236 Node tests and 28 actual CommandHistory browser checks passed. Manual desktop and 390px checks covered recovery, focus, preserved search/outcome/date filters and table scrolling with synthetic records; no native or durable writes.