From 2407217a29668d7cd1802653164223ecf567024c Mon Sep 17 00:00:00 2001 From: Ruben van der Linde Date: Mon, 24 Aug 2026 10:45:15 +0200 Subject: [PATCH 1/3] fix(docs): publish the documentation from development, not a stale branch MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This workflow triggered on `push: branches: [documentation]`. That branch exists, which is why nothing ever looked broken — but nobody updates it. Its last commit predates most of this year's work: larpinq 19 May (development is 594 commits ahead), buildiq 9 July (980 ahead). So the docs pipeline has been faithfully republishing a months-old snapshot, and reporting success every time. It is the reason larpinq.conduction.nl still says "LarpingApp" and decidiq.conduction.nl still says "Decidesk" while both repos' docs sources have said the new name since the app-id rename merged. The rename was never missed in the docs — the docs were publishing from somewhere else. Four of the twelve fleet apps (dossiq, integriq, stackiq, thematiq) already point at `development`. This brings the rest in line. Pairs with ConductionNL/.github#555, which made the reusable workflow publish to the Cloudflare Worker that actually serves the host — previously it wrote gh-pages and nothing read it. Both halves are needed: one fixes WHERE the docs go, this one fixes WHICH COMMIT they come from. --- .github/workflows/documentation.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/documentation.yml b/.github/workflows/documentation.yml index 4efaddf5..556e5e96 100644 --- a/.github/workflows/documentation.yml +++ b/.github/workflows/documentation.yml @@ -2,9 +2,9 @@ name: Documentation on: push: - branches: [documentation] + branches: [development] pull_request: - branches: [documentation] + branches: [development] jobs: deploy: From a137ccbe89a25c1e66afcf9838b8c8d43412c0b5 Mon Sep 17 00:00:00 2001 From: Ruben van der Linde Date: Mon, 24 Aug 2026 11:09:18 +0200 Subject: [PATCH 2/3] fix(docs): name the worker that actually serves this site MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The trigger fix in this PR makes the docs workflow run. This commit makes the run reach the edge. `worker-name` was never passed, so the callee derived it from `cname`. Since the app-id rename `cname` is the NEW host, and the worker that actually holds the custom domains is still named after the OLD app id. The derived name therefore points at a worker that does not exist — deploying it CREATES a second worker while both custom domains keep routing to the original. Every deploy green, reaching nobody, with the live-site verification added in ConductionNL/.github#555 as the only thing that would ever have noticed. Pinning the name also decouples the worker from `cname`, so the docs host can move to the new subdomain later without silently forking the worker. Measured today: the live host still serves the pre-rename title, which is the staleness this PR chain exists to end. --- .github/workflows/documentation.yml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/.github/workflows/documentation.yml b/.github/workflows/documentation.yml index 556e5e96..096f0878 100644 --- a/.github/workflows/documentation.yml +++ b/.github/workflows/documentation.yml @@ -18,4 +18,12 @@ jobs: # step with docs/static/CNAME. cname: keepiq.conduction.nl - docs-hosts: doriath.conduction.nl,keepiq.conduction.nl \ No newline at end of file + docs-hosts: doriath.conduction.nl,keepiq.conduction.nl + + # Named explicitly, because the comment above already knows the answer + # and the workflow did not. The callee derives the worker from `cname` + # when not told — `keepiq-docs`, which does not exist. Deploying that + # creates a SECOND worker while both custom domains keep routing to + # `doriath-docs`: every deploy green, reaching nobody. Renaming the + # worker is a Cloudflare-side move, not something this file can perform. + worker-name: doriath-docs From 05d3b8bbe16747b331efb9dc89a87f77daf6016f Mon Sep 17 00:00:00 2001 From: Ruben van der Linde Date: Mon, 24 Aug 2026 11:40:29 +0200 Subject: [PATCH 3/3] fix(docs): stop MDX parsing a placeholder as a JSX tag MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The docs build FAILS, and has been failing — it was simply never run, because the workflow triggered on a branch nobody updates. Making the trigger correct surfaced it on the first run. Error: MDX compilation failed for application-secret-requests.md Cause: Expected a closing tag for `` (27:39-27:45) `` was written as a plain-English placeholder inside a table cell. MDX reads it as an opening JSX tag, finds no closing tag, and aborts the whole client bundle — so no page of this site could publish, whatever the workflow did. Backticks the two placeholders. They now render as code, which is what a placeholder should look like anyway, and the sentence is unchanged. Verified locally: npm ci --legacy-peer-deps && npm run build now exits 0 with all 10 AI-baseline checks passing. --- docs/application-secret-requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/application-secret-requests.md b/docs/application-secret-requests.md index 36dcb47a..2e5d33a3 100644 --- a/docs/application-secret-requests.md +++ b/docs/application-secret-requests.md @@ -24,7 +24,7 @@ shows: | Column | Notes | |---|---| | Status | Pending, Fulfilled, Declined, Expired | -| Expiry | "Expires ", "Expired ", or **"No expiry"** — a link that works forever | +| Expiry | `Expires `, `Expired `, or **"No expiry"** — a link that works forever | | Token | Truncated. The full value goes to the clipboard only via **Copy fill link** | | Requested fields | The field names asked for, e.g. `key, login` |