RFC: renumber approval prompt markdown to 0002, resolve questions, align frontmatter (#13)

omarshahine · claude · kevinslin · web-flow · commit bab3348050f7 · 2026-06-21T15:40:41.000-07:00
Renumber the Approval Prompt Markdown Contract from 0005 to 0002 per
maintainer request, and resolve its three open questions into decisions:
- Underline: excluded from the canonical subset (strict cross-channel
  intersection only); core never emits underline.
- Capability: a field (approvalText) on the existing channel approval
  capability object, declared via the public SDK, defaulting to plaintext.
- Exec fence language hints: a small fixed advisory set; channels may honor
  or safely drop them.

Repo cleanup after the needs_refactoring reorg:
- Vacate numeric prefixes on all parked RFCs (doctor-health-upgrades,
  policy-conformance, imessage-channel-configuration-cleanup) so the parked
  folder is uniformly number-free pending re-proposal.
- Align frontmatter to the new RFC lifecycle by adding status/issue keys to
  the parked RFCs plus 0001-lts-release-policy and 0006-feeds.

Co-authored-by: Omar Shahine &lt;10343873+omarshahine@users.noreply.github.com&gt;
Co-authored-by: Claude Opus 4.8 (1M context) &lt;noreply@anthropic.com&gt;
Co-authored-by: kevinlin-openai &lt;kevin@dendron.so&gt;
diff --git a/rfcs/0002-approval-prompt-markdown.md b/rfcs/0002-approval-prompt-markdown.md
@@ -3,7 +3,9 @@ title: Approval Prompt Markdown Contract
 authors:
   - omarshahine
 created: 2026-05-30
-last_updated: 2026-05-30
+last_updated: 2026-06-11
+status: accepted
+issue:
 rfc_pr: https://github.com/openclaw/rfcs/pull/4
 ---
 
@@ -105,6 +107,11 @@ Underline is excluded from the core subset because most channels cannot express
 it. iMessage may still map a channel-local marker if it wants, but core does
 not emit one.
 
+Fenced code block language hints are part of the contract but advisory. Core
+emits a small fixed set (`sh` for a pending command, none or `txt` for a plain
+block). A channel may honor a hint for native syntax highlighting and must drop
+an unsupported hint safely, without altering the fenced content.
+
 ### Plugin SDK ownership
 
 The plugin SDK owns:
@@ -117,7 +124,11 @@ The plugin SDK owns:
 
 ### Channel capability
 
-Channels gain an explicit capability on their approval handler:
+Channels gain an explicit capability on their approval handler. It is a field,
+`approvalText`, on the existing channel approval capability object, declared
+through the public plugin SDK. It is not a separate standalone capability or a
+parallel registration path, which keeps the approval capability surface
+cohesive. The field defaults to `"plaintext"`.
 
 - `approvalText: "markdown"` means the channel translates the canonical subset
   into its native styling. The channel owns the translation and any escaping.
@@ -192,11 +203,19 @@ emits incidentally rather than introducing a brand new format.
 
 ## Unresolved questions
 
-- Should the canonical subset include underline given only iMessage can express
-  it, or stay at the strict cross-channel intersection and let iMessage add a
-  local marker out of band.
-- Whether the capability lives on the existing channel approval capability
-  object or as a small standalone field, and how a plugin author declares it
-  through the public SDK.
-- Whether the exec fence language hints (`sh`, `txt`) should be normalized as
-  part of the contract or left to each channel to honor or drop.
+The questions raised during initial review are resolved as follows, and the
+decisions are reflected in the Proposal above. No open questions remain.
+
+- **Underline in the canonical subset.** Resolved: no. The canonical subset
+  stays at the strict cross-channel intersection, and core never emits
+  underline. iMessage may map a channel-local marker out of band, but it is not
+  part of the contract.
+- **Where the capability lives and how it is declared.** Resolved: it is a
+  field, `approvalText`, on the existing channel approval capability object,
+  declared through the public plugin SDK and defaulting to `"plaintext"`. There
+  is no separate standalone capability or parallel registration path.
+- **Exec fence language hints.** Resolved: the contract defines a small fixed
+  set of hints (`sh` for a pending command, none or `txt` for a plain block)
+  and treats them as advisory. A channel may honor a hint for native syntax
+  highlighting and must drop an unsupported hint safely, without altering the
+  fenced content.
diff --git a/rfcs/needs_refactoring/doctor-health-upgrades.md b/rfcs/needs_refactoring/doctor-health-upgrades.md
@@ -4,6 +4,8 @@ authors:
   - giodl73-repo
 created: 2026-05-27
 last_updated: 2026-05-28
+status: accepted
+issue:
 rfc_pr: https://github.com/openclaw/rfcs/pull/1
 ---
 
diff --git a/rfcs/needs_refactoring/imessage-channel-configuration-cleanup.md b/rfcs/needs_refactoring/imessage-channel-configuration-cleanup.md
@@ -4,6 +4,8 @@ authors:
   - omarshahine
 created: 2026-05-27
 last_updated: 2026-05-29
+status: accepted
+issue:
 rfc_pr: https://github.com/openclaw/rfcs/pull/3
 ---
 
diff --git a/rfcs/needs_refactoring/policy-conformance.md b/rfcs/needs_refactoring/policy-conformance.md
@@ -4,6 +4,8 @@ authors:
   - giodl73-repo
 created: 2026-05-27
 last_updated: 2026-06-15
+status: accepted
+issue:
 rfc_pr: https://github.com/openclaw/rfcs/pull/6
 ---
 
