chore: update changelog CLI v2.39.0/v2.39.1 and Platform updates

[mintlify]

Summary

Adds changelog entries for releases published Aug 24–31: CLI v2.39.0 and v2.39.1, plus Platform changes shipped from the server.

Changes

• CLI v2.39.0 (Aug 29): --sonar-branch flag, clearer Jira credential handling, --jira-project-key whitespace tolerance, .kosli_ignore help text.
• CLI v2.39.1 (Aug 30): help text wording improvements.
• Platform: SCIM user management handed to the IdP, Spaces enabled for every org, policy-expression missing-value fix, override attestations visible to environment policies, plus UI fixes (attestations infinite scroll, Spaces tree, Environments tag filter, magic links, flows list timestamps).
• No new Terraform Provider release since v0.9.3, so no entry added.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
kosli	🟢 Ready	View Preview	Aug 31, 2026, 9:13 AM

[claude]

Claude finished @mbevc1's task in 1m 45s —— View job

---

Doc review — re-run after latest push (e582489)

• Read PR diff (git diff origin/main...HEAD)
• Read CLAUDE.md + changelog/index.mdx conventions
• Verify all internal links resolve to real pages
• Re-check whether earlier review findings were addressed
• Post findings

The last commit applied @mbevc1's suggestion and dropped the Magic links survive email scanners bullet — that resolves @dangrondahl's "internal change, behind a feature flag" note. One entry is now 76 → 75 added lines. Three findings from the earlier pass are still open.

---

changelog/index.mdx

Critical

• L15 — serialised is British spelling. CLAUDE.md mandates American spelling, and this file already uses serialized at L719. Vale's styles/Kosli/AmericanSpelling.yml swap list has no serialise entry, so CI won't flag it. Posted as a fresh inline suggestion (the previous one went stale when the diff shifted). Fix this →

Improvement

• L9–L11 — SCIM entry is a behavior removal filed under ## Updates. In SCIM-managed orgs, IdP-owned members can no longer be invited, re-invited, role-changed, or removed through Kosli. For affected admins that is a breaking change, and the file already has a ## Breaking changes heading (4 prior entries: L127, L295, L330, L344). Either move the bullet there, or split it — removal under ## Breaking changes, the opt-in toggle under ## Updates. Fix this →
• L11 — audit-log terminology. CLAUDE.md: use "audit trail", not "audit log". If this deliberately names the Audit Log UI page (as L705/L716 do), capitalize it as a proper noun so it reads as the page name. Same bullet is also the longest in the file at five sentences — the "opt back in" detail could be trimmed or moved to a linked page.

Suggestion (follow-up, not blocking)

• L49 — Spaces is announced GA but undocumented. Re-checked on this HEAD: Spaces appears nowhere under understand_kosli/, getting_started/, administration/, or integrations/, and the changelog's only two mentions are both in this PR (L49, L70). A reader who learns here that Spaces is now on for their org has nowhere to go. Same gap for SCIM user management. Every other entry in this PR links to reference docs; these two can't. Worth a follow-up issue for a Spaces concept/how-to page, linked from here once it lands.

---

Verified clean

• All 6 internal links resolve: client_reference/kosli_attest_jira.md, kosli_attest_sonar.md, kosli_snapshot_azure.md, policy-reference/environment_policy.mdx, including the #policy-expressions anchor (present at L93 of that file).
• No relative links; no new pages, so no config/navigation.json change needed.
• <Update> blocks match the existing format — tags values ("Platform", "CLI") are among the three already in use, empty description="" on Platform entries matches all 42 prior Platform entries, and entries stay in newest-first date order above the existing August 20 entry.
• Headings are sentence case and use the established New features / Updates / Bug fixes set.
• mint broken-links was not run — the mint CLI isn't installed on this runner — so link checking was done by resolving each target path and anchor directly.

Advisory review only; no changes pushed, no approval or change request submitted.
· branch mintlify/9cee9f39

[claude]

Improvement — two things on this entry:

1. Wrong section heading. This removes a capability from the UI (in SCIM-managed orgs, IdP-owned members can no longer be invited, re-invited, role-changed, or removed through Kosli). That's a breaking behavior change for affected admins, not an "Update". The file already uses a ## Breaking changes heading (4 prior entries) — this belongs there, or split so the removal sits under ## Breaking changes and keeps the rest under ## Updates.

2. audit-log terminology. CLAUDE.md: use "audit trail", not "audit log". If this deliberately names the Audit Log UI page (as prior entries at lines 706/717 do), capitalize it as a proper noun so it reads as the page name rather than generic prose.

Also worth tightening — at five sentences this is the longest bullet in the file; the "opt back in" detail could move to a second sentence or a linked doc page.

[claude]

Improvement (docs gap, follow-up — not blocking) — Spaces is announced as generally available here, but it is undocumented anywhere on the site: grep -ri spaces across understand_kosli/, getting_started/, and administration/ returns only unrelated hits (the word "spaces", "namespaces"), and this is the changelog's first mention of the feature. A reader who learns from this entry that Spaces is now on for their org has nowhere to go to learn how to use it.

Every other entry in this PR links to reference docs (/client_reference/..., /policy-reference/...); this one and the SCIM entry can't, because the pages don't exist. Suggest opening a follow-up issue for a Spaces concept/how-to page (and one for SCIM user management) and linking it from here once it lands.

[dangrondahl]

Although nice, this is an internal change (behind a feature flag).