DELETED Markdown linting POC

.markdownlint-cli2.yaml

@@ -6,8 +6,21 @@ ignores:
   - site/**
   - .venv/**
 
-  # CLAUDE.md is just an @-include pointing at AGENTS.md, so it fails MD041 (no H1)
+  # CLAUDE.md files are just an @-include pointing at AGENTS.md, so they fail MD041 (no H1)
   - CLAUDE.md
+  - .github/workflows/CLAUDE.md
 
   # Generated from the OCS OpenAPI schema by the update-api-docs workflow; not hand-edited
   - docs/api/**
+
+# AGENTS.md files are read by Claude Code as system-context instructions, not rendered as
+# docs — same trust model as .claude/agents/*.md and .github/templates/*.md. They share a
+# directory with human-facing docs (README.md, README-*.md), so scope this to the exact
+# files rather than a directory cascade.
+overrides:
+  - filter:
+      - AGENTS.md
+      - .github/workflows/AGENTS.md
+    config:
+      extends: ./.markdownlint-prompts.yaml
+    combine: replace

.markdownlint.yaml

@@ -12,7 +12,7 @@ MD007: false
 
 # Line length — reduce progressively after long lines are fixed
 MD013:
-  line_length: 750
+  line_length: 650
   code_blocks: false
   tables: false
   headings: false

docs/changelog.md

@@ -22,12 +22,14 @@ hide:
 * **NEW** Macro-enabled Excel workbooks (`.xlsm`) can now be attached to a chat and uploaded to a [collection](concepts/collections/index.md). They were previously rejected as an unsupported file type. As with other documents, the file is never executed — only its extracted text is sent to the LLM.
 * **NEW** The notifications list now has toggle buttons for filtering by level (Info, Warning, Error) and, if you belong to fewer than three teams, by team — alongside the existing filter panel. A notification that has occurred more than once shows a count of how many times it recurred (`×3`), and the notification detail page now names the team in its breadcrumb.
 * **NEW** You can now sample the traces sent to Langfuse instead of sending every conversation turn, using a team-wide **Sample rate** on the Langfuse tracing provider and a per-chatbot **Trace sample rate** override that inherits the team default when left blank. Setting a chatbot's rate to `0.0` stops its Langfuse traces entirely. Builtin tracing is unaffected and still records every turn, and rate changes take effect on the next turn. The `trace_sample_rate` field is also available on the v2 chatbots write API. See [Configure Langfuse Trace Sampling](how-to/configure_langfuse_trace_sampling.md).
-* **NEW** A chatbot's consent form can now be collected through the [Chat API](api/v1/index.md) rather than the separate web page. Starting or polling a session returns a `consent` block saying whether consent is still needed and what the form says, a new `POST /api/chat/{session_id}/consent/` endpoint records that the participant accepted it, and sending a message or uploading a file is refused until they have. Republishing the chatbot with an edited consent form asks the participant again. This applies only to chat widgets on version 0.13.0 or later, which will carry the consent panel — existing embeds are unaffected, as are API key and OAuth callers. See [Consent Forms](concepts/consent.md).
+* **NEW** A chatbot's consent form can now be collected through the [Chat API](api/v1/index.md) rather than the separate web page. Starting or polling a session returns a `consent` block saying whether consent is still needed and what the form says, a new `POST /api/chat/{session_id}/consent/` endpoint records that the participant accepted it, and sending a message or uploading a file is refused until they have.
+Republishing the chatbot with an edited consent form asks the participant again. This applies only to chat widgets on version 0.13.0 or later, which will carry the consent panel — existing embeds are unaffected, as are API key and OAuth callers. See [Consent Forms](concepts/consent.md).
 * **CHANGE** The chatbot inspect API (`GET /api/v2/chatbots/{id}/inspect/`) no longer returns an `assistant` key on a pipeline node, and the `AssistantNodeParams` schema has been removed. Only clients inspecting pipelines that contain an assistant node are affected — those nodes are still listed, with their type reported as before and their stored settings returned in the generic node params shape (minus the internal assistant id). See the [Chatbots API reference](api/v2/chatbots.txt).
 * **BUG** Publishing a version of a chatbot now keeps a copy of its consent form as it read at that moment. Previously every published version pointed at the current working form, so editing that form also changed the wording shown by versions published before the edit. Versions published before this fix keep using the working form until the chatbot is published again.
 
 ## Sep 2, 2026
-* **CHANGE** The OpenAI Assistants pages have been removed. The **Assistants** entry is gone from the sidebar, and assistants can no longer be created, viewed, edited or archived in Open Chat Studio — the assistant URLs now return a "not found" error. Assistants no longer appear in the delete-team confirmation, no longer block deleting an LLM provider or a custom action, and no longer appear in deprecated-model reporting, and the file-upload controls that assistants added to the chat input bar are gone. File links in historical chat messages now show as plain text instead of downloads. Chatbots and pipelines that use an assistant node still open and still run as before. See [Migrate Assistants](how-to/assistants_migration.md).
+* **CHANGE** The OpenAI Assistants pages have been removed. The **Assistants** entry is gone from the sidebar, and assistants can no longer be created, viewed, edited or archived in Open Chat Studio — the assistant URLs now return a "not found" error. Assistants no longer appear in the delete-team confirmation, no longer block deleting an LLM provider or a custom action, and no longer appear in deprecated-model reporting, and the file-upload controls that assistants added to the chat input bar are gone.
+File links in historical chat messages now show as plain text instead of downloads. Chatbots and pipelines that use an assistant node still open and still run as before. See [Migrate Assistants](how-to/assistants_migration.md).
 
 ## Sep 1, 2026
 * **NEW** An embedded widget channel can now require an **OAuth** token instead of its embed key, using the new **Credential mode** setting on the channel. In OAuth mode every request is validated against a token minted by your own backend, the embed snippet shown in Open Chat Studio includes a sample `authTokenProvider` implementation, and the widget must be on version 0.12.0 or later. Existing channels keep the embed-key mode they already have. Leaving the channel's allowed domains blank marks the channel as a server-only integration, so any request from a browser is refused. See [OAuth credential mode](chat_widget/reference.md#oauth-credential-mode).
@@ -54,7 +56,8 @@ hide:
 * **BUG** Fixed an error raised by the code in a [Python node](tech-hub/python_node.md) causing the message to fail without a reply. The participant now receives a generic error response, and the error is recorded against the message so you can see what went wrong.
 
 ## Aug 20, 2026
-* **CHANGE** Turning off a channel's **Enabled** toggle now stops new conversations and bot-initiated messages, where before it only stopped incoming ones. Previously a disabled channel still allowed new conversations to be started (from the chat widget, the public web chat link, Slack, or the chatbot management pages) and still sent out scheduled messages, event action messages and API-triggered messages. New sessions on a disabled channel are now refused, and bot-initiated messages to a disabled channel are no longer sent. Two API endpoints are still exceptions — see [Known limitations](how-to/disable_a_channel.md#known-limitations). See [Disabling a channel](concepts/channels.md#disabling-a-channel).
+* **CHANGE** Turning off a channel's **Enabled** toggle now stops new conversations and bot-initiated messages, where before it only stopped incoming ones. Previously a disabled channel still allowed new conversations to be started (from the chat widget, the public web chat link, Slack, or the chatbot management pages) and still sent out scheduled messages, event action messages and API-triggered messages.
+New sessions on a disabled channel are now refused, and bot-initiated messages to a disabled channel are no longer sent. Two API endpoints are still exceptions — see [Known limitations](how-to/disable_a_channel.md#known-limitations). See [Disabling a channel](concepts/channels.md#disabling-a-channel).
 
 ## Aug 18, 2026
 * **CHANGE** When several branches merge into one node, that node now takes its input from the branch that arrived most recently, and `node_inputs` holds every input that has arrived so far instead of just one. Previously the input depended on the order the connections happened to be drawn, so the same graph could feed a merge node a different branch — any node with more than one incoming connection may now receive a different input than before. See [Which input a node receives](concepts/pipelines/parallel.md#which-input-a-node-receives).