docs: rename API tag to Platform and improve changelog workflow

.mintlify/workflows/update-changelog.md

@@ -21,10 +21,22 @@ Write a changelog post under changelog/index.mdx for this week based on what shi
 Make sure to update resources and data sources in `terraform-reference/` to match `kosli-dev/terraform-provider-kosli`. Make sure when copy documentation across to use Mintlify formatting.
 
 Label should be the date the workflow runs, like "March 16, 2026". Description should be the version number of the release, like "v0.3.0".
-Tags should be the product(s) affected by the release, like ["CLI"], ["API"], or ["Terraform Provider"].
+Tags should be the product(s) affected by the release:
+- kosli-dev/cli → `["CLI"]`
+- kosli-dev/terraform-provider-kosli → `["Terraform Provider"]`
+- kosli-dev/server → `["Platform"]`
 
 The changelog is about changes to the product, not changes to the docs.
 
-Do not include any internal-only information—no private repository file paths, directory structures, code snippets, internal function names, or implementation details. Only include updates that affect end users. Include a description of the change and what it means for users. Organize the changelog with new features first, then updates, then bug fixes. If you're ever unsure about the structure, review recent changelog updates and follow that style and format.
+Only include updates that affect end users. Do not include internal-only information such as:
+- Private repository file paths or directory structures
+- Code snippets, internal function names, or implementation details
+
+For each change, describe what changed and what it means for users. Organize entries in this order:
+1. New features
+2. Updates
+3. Bug fixes
+
+If unsure about the structure, review recent changelog updates and follow that style and format.
 
 Be polite and terse. The changelog must be skimmable and quick to read. Include relevant links to docs pages.

changelog/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Changelog"
 description: "Release notes for Kosli products."
 rss: true
 ---
 
@@ -9,7 +9,7 @@
 ## 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,13 +24,13 @@
 
 ## 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)
 
 </Update>
 
-<Update label="March 30, 2026" description="" tags={["API"]}>
+<Update label="March 30, 2026" description="" tags={["Platform"]}>
 
 ## New features
 
@@ -47,8 +47,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)
 
@@ -81,12 +81,12 @@
 
 </Update>
 
-<Update label="March 23, 2026" description="" tags={["API"]}>
+<Update label="March 23, 2026" description="" tags={["Platform"]}>
 
 ## 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 +105,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 +128,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 +144,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)