From 7a794e92a71bdea3474e98e1f2022d3cbba5339a Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Mon, 22 Jun 2026 03:13:04 +0000 Subject: [PATCH] docs(KOB-1): release-note draft from docs-writer skill --- .../drafts/KOB-1-release-note-draft.adoc | 56 +++++++++++++++++++ 1 file changed, 56 insertions(+) create mode 100644 docs/modules/release-notes/pages/drafts/KOB-1-release-note-draft.adoc diff --git a/docs/modules/release-notes/pages/drafts/KOB-1-release-note-draft.adoc b/docs/modules/release-notes/pages/drafts/KOB-1-release-note-draft.adoc new file mode 100644 index 00000000..5bfd4e6f --- /dev/null +++ b/docs/modules/release-notes/pages/drafts/KOB-1-release-note-draft.adoc @@ -0,0 +1,56 @@ += Release note draft — KOB-1 (blocked: no source evidence) +:navtitle: KOB-1 release-note draft + +// NOT FOR PUBLICATION. +// Generated by the Robot Ranch docs-workflow (Ledger / docs-writer) in a CI context. +// This branch is the review surface for the docs team. Do not merge as-is. +// Status: Blocked — no source evidence was available for ticket KOB-1. + +[IMPORTANT] +==== +This is an automated *draft placeholder*, not a publishable release note. The +docs-writer skill (Ledger) could not produce a release note because no source +evidence for *KOB-1* was available at generation time. Resolve the open +questions below before drafting. +==== + +== Mode + +`release-note` (specified by the workflow trigger). + +== Source evidence used + +None. + +* No `features/KOB-1*` spec folder exists on the `.ai` `main` branch. +* No Jira/Atlassian integration was available in this run, so the KOB-1 ticket could not be fetched or normalized (Dish / `jira-draft` could not run). +* No PR summary, diff summary, or manually supplied ticket text was provided. + +== Draft output + +No draft produced. + +Content is not drafted without source evidence. Inventing a feature title, +summary, highlights, or availability for KOB-1 would violate the docs-writer +core rules: do not invent product details, and do not proceed without source +evidence. + +== User-facing impact summary + +Cannot be determined. The user-visible change introduced by KOB-1 is unknown +because no source evidence describes it. + +== Open questions or verification needed + +. What feature, fix, or behavior change does KOB-1 cover? Provide the Jira ticket summary, description, and acceptance criteria. +. Is this a new feature/enhancement (title, summary, optional highlights, availability) or a bug fix/smaller improvement (short grouped item)? +. Which release version does KOB-1 ship in? This determines the target `all-releases/.adoc` page and its `nav.adoc` entry. +. What is the user-facing impact, and what is the exact affected product surface (precise UI and product names)? +. Are there availability constraints — deployment type, subscription, enablement, or required permissions? +. Does KOB-1 also need supporting documentation (concept or procedure) beyond the release note? + +== How to proceed + +. Supply KOB-1 source evidence: add a `features/KOB-1*` spec folder on `.ai`, or provide the Jira ticket content or PR summary directly. +. Re-run the Robot Ranch release-note flow (Dish, then Ledger) with that evidence. +. Ledger replaces this placeholder with a real release-note entry on the correct `all-releases/.adoc` page, with a matching `nav.adoc` entry.