From 594779aadba7d709e755df89d57051d251065c9b Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Mon, 22 Jun 2026 03:14:01 +0000 Subject: [PATCH] docs(KOB-2): release-note draft from docs-writer skill --- .../pages/all-releases/_kob-2-draft.adoc | 66 +++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 docs/modules/release-notes/pages/all-releases/_kob-2-draft.adoc diff --git a/docs/modules/release-notes/pages/all-releases/_kob-2-draft.adoc b/docs/modules/release-notes/pages/all-releases/_kob-2-draft.adoc new file mode 100644 index 00000000..6ab58dda --- /dev/null +++ b/docs/modules/release-notes/pages/all-releases/_kob-2-draft.adoc @@ -0,0 +1,66 @@ +// DRAFT — NOT FOR PUBLICATION +// Generated by the Robot Ranch docs-workflow (Ledger / docs-writer) in release-note mode. +// This file is intentionally underscore-prefixed so Antora does NOT publish it, and it is +// intentionally NOT added to nav.adoc. It is a review artifact for the docs team only. +// BLOCKING: No source evidence was available for KOB-2 at generation time. Do not publish +// until a writer supplies ticket evidence and the open questions below are resolved. + += KOB-2 release note draft (blocked — no source evidence) +:navtitle: KOB-2 release note draft + +[IMPORTANT] +==== +This is an unverified, unpublished draft. Ledger could not retrieve any source +evidence for KOB-2 and therefore did not draft release-note content. Drafting was +deliberately withheld rather than fabricated. See the open questions below. +==== + +== Mode + +`release-note` (specified by the workflow trigger). + +== Source evidence used + +None. No usable source evidence could be obtained for KOB-2: + +* *Jira (Dish / jira-draft):* The Atlassian MCP server is not connected in this + headless CI session (interactive OAuth), so the KOB-2 ticket could not be + fetched or normalized. +* *Spec folder:* No `features/KOB-2*` folder exists on the `.ai` `main` branch. +* *Deployment PR:* None supplied. +* *Docs repo:* No existing KOB-2 reference found in the documentation repository. + +== Draft output + +No release-note content was drafted. + +Per the docs-writer core rules, Ledger does not proceed without source evidence and +does not invent product details, feature names, UI labels, availability, or +user-facing behavior. With zero evidence for KOB-2, any release note would be +fabricated, so none was written. + +== User-facing impact summary + +Cannot be determined. The user-visible change introduced by KOB-2 is unknown +without source evidence. + +== Open questions or verification needed + +. What is the actual scope of KOB-2? (summary, description, acceptance criteria) +. Is KOB-2 user-facing at all, or internal-only? If internal-only, a release note + may not be warranted. +. If user-facing: is it a new feature / enhancement, or a bug fix / smaller + improvement? This determines the release-note shape. +. Which release version does KOB-2 ship in? (No version is known, so this draft is + not yet a numbered `all-releases/.adoc` entry and is not wired into + `nav.adoc`.) +. Does KOB-2 also require a full doc page (concept/procedure), or a release note + only? +. Availability conditions (subscription, device type, permission, enablement), if any. + +== Next action + +Provide the KOB-2 ticket evidence (re-run with the Atlassian MCP authenticated, add a +`features/KOB-2*` spec folder, or paste ticket content), then re-run Ledger to produce +the actual release note, assign it the correct version filename, and add it to +`nav.adoc`.