docs: add April 6 changelog and update Terraform reference

changelog/index.mdx

@@ -1,15 +1,60 @@
 ---
 title: "Changelog"
 description: "Release notes for Kosli products."
 rss: true
 ---
 
+<Update label="April 6, 2026" description="v0.5.0" tags={["Terraform Provider"]}>
+
+## New features
+
+- **`kosli_flow` resource and data source** — manage Kosli [flows](/getting_started/flows) as Terraform resources. Define name, description, and YAML template inline or via `file()`. The data source lets you query existing flows and reuse their templates. See the [resource](/terraform-reference/resources/flow) and [data source](/terraform-reference/data-sources/flow) reference.
+
+[View on GitHub](https://github.com/kosli-dev/terraform-provider-kosli/releases/tag/v0.5.0)
+
+</Update>
+
+<Update label="April 6, 2026" description="v2.15.1" tags={["CLI"]}>
+
+## New features
+
+- **`kosli evaluate input`** — evaluate a local JSON file (or stdin) against a Rego policy with no API dependency. Enables local policy development and fast iteration without a running Kosli server. See the [evaluate input](/client_reference/kosli_evaluate_input) reference.
+- **`--params` flag for policy evaluation** — pass configuration data (thresholds, expected counts, etc.) to Rego policies via `--params` on [`kosli evaluate trail`](/client_reference/kosli_evaluate_trail), [`kosli evaluate trails`](/client_reference/kosli_evaluate_trails), and [`kosli evaluate input`](/client_reference/kosli_evaluate_input). Accepts inline JSON or a file reference. Parameters are available as `data.params` in the policy.
+- **npm installation** — the Kosli CLI is now available as an npm package (`@kosli/cli`), making it easy to install in JavaScript/Node.js toolchains.
+
+## Bug fixes
+
+- Fixed Docker API version negotiation — the CLI now automatically negotiates the Docker API version with the host daemon, preventing compatibility errors after SDK upgrades.
+- Fixed AWS API rate limiting — snapshot commands for ECS, S3, and Lambda environments now use adaptive retry with up to 10 attempts, preventing failures under heavy API load.
+- Fixed git HEAD resolution in linked worktrees.
+
+[View on GitHub](https://github.com/kosli-dev/cli/releases/tag/v2.15.1)
+
+</Update>
+
+<Update label="April 6, 2026" description="" tags={["Platform"]}>
+
+## New features
+
+- **Deployment list** — the repository releases page now includes a deployments tab showing a paginated list of deployments with artifact details, commit links, replaced artifacts, and compliance status.
+- **Filter deployments by environment** — filter the deployment list and metrics by specific environments on the repository releases page.
+
+## Updates
+
+- Redesigned the repository run page with improved layout, hover states, and rich tooltips showing artifact fingerprints, snapshot references, and commit details.
+
+## Bug fixes
+
+- Fixed an error when viewing deployment details for artifacts with a missing replaced snapshot index.
+
+</Update>
+
 <Update label="March 30, 2026" description="v2.13.2" tags={["CLI"]}>
 
 ## Updates
 
 - **Removed deprecated `kosli expect deployment` command** — deployment expectation is no longer required for compliance. If your pipelines still reference this command, remove or replace it.
 - **CI-ready Docker image** — a new Alpine-based Dockerfile is available for use as a CI runner image (e.g., GitLab CI), providing the Kosli CLI alongside common CI tooling.
 
 ## Bug fixes
 
@@ -24,7 +69,7 @@
 
 ## Bug fixes
 
 - Fixed `type_schema` handling — the provider now correctly reads JSON objects returned by the API, replacing the previous Python repr string workaround.
 
 [View on GitHub](https://github.com/kosli-dev/terraform-provider-kosli/releases/tag/v0.4.2)
 
@@ -47,8 +92,8 @@
 ## New features
 
 - **`kosli_action` resource and data source** — manage webhook notification actions as Terraform resources. Create, update, and import actions by name, and read existing actions to reference in your configurations.
 - **`kosli_policy` resource and data source** — manage Kosli policies as Infrastructure-as-Code. The data source exposes the policy name, description, content, and latest version.
 - **`kosli_policy_attachment` resource** — manage the relationship between policies and environments, letting you attach and detach policies declaratively.
 
 [View on GitHub](https://github.com/kosli-dev/terraform-provider-kosli/releases/tag/v0.4.0)
 
@@ -86,7 +131,7 @@
 ## New features
 
 - **Attestation evidence download** — a new API endpoint lets you download evidence files attached to attestations, making it easier to retrieve and audit attestation data programmatically.
 - **Snapshotter role** — a new [Snapshotter role](/administration/managing_users/roles_in_kosli) is available for users who need to create environment snapshots and manage service accounts without full member permissions. Ideal for environment and operations teams.
 
 </Update>
 
@@ -105,7 +150,7 @@
 ## New features
 
 - **`kosli evaluate trail` and `kosli evaluate trails`** — evaluate one or more trails against a [Rego](https://www.openpolicyagent.org/docs/latest/policy-language/) policy and get a structured pass/fail decision. Use `--attestations` to filter which attestations are checked, and `--output json` for machine-readable results. Exit code reflects the policy decision, making it ideal for CI/CD gates. See the [evaluate trail](/client_reference/kosli_evaluate_trail) and [evaluate trails](/client_reference/kosli_evaluate_trails) reference for details.
 - **Multi-environment K8s reporting** — `kosli snapshot k8s` now accepts a `--config-file` flag to report multiple Kosli environments in a single command. Define environment-to-namespace mappings in a YAML file instead of running the command once per environment. See the [snapshot k8s](/client_reference/kosli_snapshot_k8s) reference.
 - **Helm chart v2.0.0** — the [k8s-reporter Helm chart](/helm/k8s_reporter) now uses a `reporterConfig.environments` list, enabling multi-environment reporting from a single chart installation. This is a breaking change from v1.x — see the chart README for migration steps.
 
 [View on GitHub](https://github.com/kosli-dev/cli/releases/tag/v2.12.0)
@@ -128,7 +173,7 @@
 
 - **`kosli_logical_environment` resource** — create and manage logical environments that aggregate multiple physical environments into a single view.
 - **`kosli_logical_environment` data source** — query details of existing logical environments.
 - **Drift detection for logical environments** — Kosli now detects when the `included_environments` of a logical environment change outside of Terraform.
 - **User agent header** — the provider now sends a versioned user agent on every API request, improving diagnostics.
 
 ## Bug fixes
@@ -144,7 +189,7 @@
 
 ## New features
 
 - **`kosli_environment` resource** — create and manage physical Kosli environments (K8S, ECS, S3, docker, server, lambda) as Terraform resources.
 - **`kosli_environment` data source** — query details of existing physical environments.
 
 [View on GitHub](https://github.com/kosli-dev/terraform-provider-kosli/releases/tag/v0.2.0)

docs.json

@@ -498,6 +498,7 @@
                 "pages": [
                   "terraform-reference/resources/environment",
                   "terraform-reference/resources/logical_environment",
+                  "terraform-reference/resources/flow",
                   "terraform-reference/resources/custom_attestation_type",
                   "terraform-reference/resources/action",
                   "terraform-reference/resources/policy",
@@ -509,6 +510,7 @@
                 "pages": [
                   "terraform-reference/data-sources/environment",
                   "terraform-reference/data-sources/logical_environment",
+                  "terraform-reference/data-sources/flow",
                   "terraform-reference/data-sources/custom_attestation_type",
                   "terraform-reference/data-sources/action",
                   "terraform-reference/data-sources/policy"

terraform-reference/data-sources/flow.mdx

@@ -0,0 +1,52 @@
+---
+title: "kosli_flow data source"
+description: "Fetches details of an existing Kosli flow. Use this data source to reference flow configurations and templates."
+icon: "database"
+---
+
+Fetches details of an existing Kosli flow. A flow represents a business or software process that requires change tracking.
+
+## Example usage
+
+```terraform
+terraform {
+  required_providers {
+    kosli = {
+      source = "kosli-dev/kosli"
+    }
+  }
+}
+
+# Query an existing flow
+data "kosli_flow" "example" {
+  name = "my-application-flow"
+}
+
+# Create a new flow reusing the template from an existing one
+resource "kosli_flow" "copy" {
+  name        = "my-application-flow-copy"
+  description = data.kosli_flow.example.description
+  template    = data.kosli_flow.example.template
+}
+
+output "flow_name" {
+  description = "The name of the flow"
+  value       = data.kosli_flow.example.name
+}
+
+output "flow_template" {
+  description = "The YAML template of the flow"
+  value       = data.kosli_flow.example.template
+}
+```
+
+## Schema
+
+### Required
+
+- `name` (String) The name of the flow to query.
+
+### Read-only
+
+- `description` (String) The description of the flow.
+- `template` (String) YAML template defining the flow structure (trails, artifacts, attestations).

terraform-reference/resources/flow.mdx

@@ -0,0 +1,77 @@
+---
+title: "kosli_flow resource"
+description: "Manages a Kosli flow. Flows represent business or software processes that require change tracking."
+icon: "cube"
+---
+
+Manages a Kosli flow. A flow represents a business or software process that requires change tracking. It lets you monitor changes across all steps within a process or focus on a subset of critical steps.
+
+<Note>
+The `template` attribute accepts a YAML string defining the flow template structure. You can load it from a file using the `file()` function: `template = file("template.yml")`. Minor YAML formatting differences between what you provide and what the API returns may result in a no-op change being shown in plans.
+</Note>
+
+## Example usage
+
+```terraform
+terraform {
+  required_providers {
+    kosli = {
+      source = "kosli-dev/kosli"
+    }
+  }
+}
+
+# Minimal flow with only a name
+resource "kosli_flow" "minimal" {
+  name = "my-service"
+}
+
+# Flow with description
+resource "kosli_flow" "with_description" {
+  name        = "api-service"
+  description = "CD pipeline for the API service"
+}
+
+# Flow with a YAML template defining trails and attestations
+# The template can also be loaded from a file: template = file("template.yml")
+resource "kosli_flow" "with_template" {
+  name        = "backend-service"
+  description = "Backend service CD pipeline with full attestation template"
+
+  template = <<-YAML
+version: 1
+trail:
+  attestations:
+    - name: pull-request
+      type: pull_request
+    - name: unit-tests
+      type: generic
+  artifacts:
+    - name: docker-image
+      attestations:
+        - name: sbom
+          type: generic
+        - name: security-scan
+          type: snyk
+YAML
+}
+```
+
+## Import
+
+Flows can be imported using their name:
+
+```shell
+terraform import kosli_flow.example my-flow-name
+```
+
+## Schema
+
+### Required
+
+- `name` (String) Name of the flow. Must be unique within the organization. Changing this will force recreation of the resource.
+
+### Optional
+
+- `description` (String) Description of the flow. Explains the purpose and context of this pipeline.
+- `template` (String) YAML template defining the flow structure (trails, artifacts, attestations). Can be provided as an inline heredoc or loaded from a file using `file()`. If omitted, the flow is created without a template.