Squidie v0.1.3

What's Changed

• Prepared Squidie 0.1.3 release artifacts.
• Fixed ExSlop DocFalseOnPublicFunction check suppression scope to reduce CI false positives during code quality checks.
• Bumped library version and installation docs from 0.1.2 to 0.1.3.

Squidie 0.1.2

Rebranded Squid Mesh to Squidie, renamed the package/module tree, and prepared the new Hex release.

v0.1.1

Changed

• Polished README setup and positioning around the embedded runtime, host-owned executor loops, and optional Bedrock-backed delivery.
• Clarified Bedrock queue, lease, heartbeat, retry, and dead-letter setup with step-by-step examples.
• Moved Jido primitive boundary guidance into the Jido runtime architecture guide and removed stale roadmap/refactor wording from architecture docs.
• Expanded production readiness guidance into a feature readiness map focused on adoption planning, operational ownership, and rollout evidence.
• Linked storage adapter guidance directly to the storage strategy document.
• Split dense dynamic-work README guidance into visual and tabular reference material.
• Excluded local Dialyzer PLT artifacts from the Hex package file list.

Verification

• mix precommit
• mix docs
• mix hex.build

v0.1.0

Breaking

• The concise runtime API is now canonical.

Runtime APIs and Control Flow

• Runtime command signals, the Jido signal adapter, and signal-interpreter routing for run controls.
• Durable command receipts and command history in run inspection, including actor, metadata, idempotency, and occurrence details.
• Numeric transition conditions for workflow routing.
• Workflow definition version metadata on started runs and inspection surfaces.
• The safe action registry for executable runtime-authored workflow specs.
• Runtime-authored workflow start APIs through normalized specs, with safe action registry boundaries and host-app example coverage.

Durable Execution

• Durable child workflow runs and child-run graph links for parent/child inspection.
• Saga compensation callbacks and compensation recovery metadata for failure recovery inspection.
• Deferred continuation runtime semantics and regression coverage for deferred continuation lifecycle behavior.
• Executor-owned journal heartbeats for long-running claimed attempts.
• SLA deadline contracts for workflow steps, including persisted deadline metadata, due-soon and escalation timestamps, read-model summaries, graph inspection output, explanations, and host-app example coverage.

Visual Editing and Dynamic Work

• Public dynamic work recording, dynamic work inspection metadata, executable dynamic work scheduling, and validation for dynamic work actions.
• Dynamic work preview APIs, preview overlays, and graph overlays for visual workflow tooling.
• Visual editor spec round trips, editor spec action-key validation, and editor draft diffing.

Observability and Visibility

• Actor-scoped read visibility, node redaction, and comprehensive actor visibility documentation.
• Bedrock host-app integration coverage for queue delivery, leases, heartbeats, retries, cron delivery, and SLA metadata.

Documentation and Release Positioning

• Install snippets now reference 0.1.0.
• Public status wording now describes the supported 0.1.x journal runtime instead of using the previous evaluation-only warning.
• README setup guidance now distinguishes the built-in journal runtime from optional external queue/leasing backends such as Bedrock.
• Host leasing and Bedrock setup docs now describe the executor, queue, lease, heartbeat, retry, and dead-letter boundaries more explicitly.
• The README, first-run path, workflow examples, and core docs were tightened around current journal runtime usage.
• Getting Started Livebook dependency setup no longer pins Squid Mesh to a local prerelease dependency.
• The storage adapter contract and Jido primitive/signal boundaries are now documented explicitly.

Fixes

• Retry scheduling tolerates invalid deadline metadata by omitting inspection-only retry deadline data instead of crashing the executor failure path.
• Cron window signal identity and runtime signal validation edges have dedicated regression coverage.

v0.1.0-beta.3

Changed

• README community links now live in a dedicated Community section instead of
  the status badge row.
• Install snippets now reference 0.1.0-beta.3.

v0.1.0-beta.2

Added

• UI-friendly graph inspection map serialization through
  SquidMesh.Runs.GraphInspection.to_map/1, including documented node and edge
  shapes for dashboards, CLIs, and visual workflow tools.
• Reference workflow documentation for approval, recovery, dependency, saga,
  and scheduled workflow examples in the minimal host app.
• Getting Started and Workflow Authoring Livebooks that execute against the
  journal runtime and show visible attempts, scheduled wakeups, graph output,
  manual approval state, normalized specs, dependency joins, and nested input
  mappings.
• Discord notification workflow regression coverage for multiline message
  payloads.

Changed

• Documentation is reorganized around reader intent, with clearer README entry
  points, a structured docs home, grouped ExDoc extras, updated observability
  guidance, and Mermaid architecture diagrams.
• Getting-started and workflow-authoring examples now keep a consistent fantasy
  workflow thread while demonstrating the current DSL and runtime inspection
  APIs.
• Dependency versions were refreshed for Jido, Req, and ExDoc within the
  existing supported constraints.

Fixed

• Discord notification payloads now send real multiline content instead of
  literal escaped newline sequences.
• Documentation snippets that inspect, cancel, replay, explain, or graph runs
  now consistently use the current run_id field.

v0.1.0-beta.1

First beta release of the journal-backed runtime.

Highlights:

• the runtime is now Jido-native and journal-backed
• the minimal host and Bedrock example apps exercise the shipped contract
• README, host app integration docs, and changelog now point at 0.1.0-beta.1

See CHANGELOG.md for the full slice history.

v0.1.0-alpha.7

Added

• Pluggable executor boundary for step execution, delayed scheduling, redelivery, and cron activation.
• Native SquidMesh.Step modules with raw Jido.Action support retained as an explicit interop path.
• Durable dispatch protocol documentation and runtime projection invariants.
• Runic workflow planner boundary, Jido storage journal boundary, durable rebuild fences, and rebuildable runtime agent checkpoints.

Changed

• Example workflows now use native Squid Mesh steps by default.
• README and host app setup snippets now reference 0.1.0-alpha.7.

Fixed

• Planner input/output mappings now align with workflow mappings.
• Dispatch projection validation, journal replay decoding, and agent replay recovery are more defensive.

v0.1.0-alpha.6

Added

• Saga compensation callbacks with compensate: SomeAction, executed in reverse completion order after downstream terminal failure with persisted recovery history.
• Failure-route recovery markers with recovery: :compensation | :undo on error transitions, plus :compensation_routed and :undo_routed audit events.
• Local repo transaction groups for custom steps through transaction: :repo, wrapping the step action in the configured repo transaction.
• Minimal host app examples and smoke coverage for saga checkout, gateway credit compensation routing, and local ledger transaction commit/rollback.

Changed

• Workflow authoring, operations, README, and host app documentation now distinguish saga rollback, same-step failure routing, undo, and local repo transaction boundaries.
• Runtime failure and compensation paths now preserve more recovery metadata for inspection and explainability.

Fixed

• Hardened compensation outcome handling and terminal target serialization for failure recovery routes.
• Nested exception structs in step error details no longer crash error normalization.

Notes

• This remains an alpha release. transaction: :repo is a local host repo boundary only; it is not a distributed transaction across durable workflow progress, Oban dispatch, external systems, or compensation callbacks.

v0.1.0-alpha.5

Added

• Step recovery markers with irreversible: true and compensatable: false
  for workflows that perform side effects which cannot be safely replayed by
  default.
• Persisted recovery policy on step runs, exposed through run inspection,
  declared step state, and run explanations.
• Replay safety checks that block SquidMesh.replay_run/2 after completed
  irreversible or non-compensatable steps unless the caller passes
  allow_irreversible: true.
• Exported formatter rules for Squid Mesh workflow DSL calls, plus host app
  setup guidance for importing them.

Changed

• Workflow examples and documentation now use the exported DSL formatter style
  without unnecessary parentheses.
• The minimal host app marks its notification step as non-compensatable.

Fixed

• Recovery marker validation no longer emits a misleading conflict error for
  non-boolean marker values.
• Persisted recovery policy normalization now preserves the invariant that
  irreversible steps are non-compensatable.
• Replay approval requires allow_irreversible: true exactly; other truthy
  values no longer bypass the unsafe replay guard.

Notes

• This remains an alpha release. Existing alpha host apps that already installed
  earlier Squid Mesh migrations should reinstall from the current schema or
  apply an equivalent local migration before writing new step runs.