@devcxl/opencode-cabbage 1.3.0 → 2.0.0

package/vendor/cabbage/cabbage_cli/assets/integrations/cabbage.yml

@@ -0,0 +1,127 @@
+# Generated template for cabbage projects. If this project does not publish a
+# documentation site, delete the `deploy-pages` job (and the documentation steps
+# of `validate-and-test`); CI stays green because those steps are conditional.
+# The test step below runs Python's unittest when tests/ exists; adapt it to your
+# project's test runner so a missing test run is surfaced instead of silent.
+name: CI & Docs Deployment
+
+on:
+  push:
+    branches:
+      - master
+      - main
+  pull_request:
+    branches:
+      - master
+      - main
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: false
+
+jobs:
+  validate-and-test:
+    name: Test & Validate
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+
+      - name: Install Python dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ]; then
+            python -m pip install -r requirements.txt
+          else
+            echo "No requirements.txt; skipping project dependencies."
+          fi
+          python -m pip install PyYAML
+
+      - name: Run Test Suite
+        run: |
+          if [ -d tests ]; then
+            python -m unittest discover tests
+          else
+            echo "::warning title=Test suite skipped::no tests/ directory found; adapt the Run Test Suite step to this project's test runner so the test stage actually runs."
+          fi
+
+      - name: Validate Cabbage Changes
+        run: |
+          if [ -d ".cabbage/tooling" ]; then
+            export PYTHONPATH=".cabbage/tooling${PYTHONPATH:+:$PYTHONPATH}"
+            python -m cabbage_cli validate --all
+          elif command -v cabbage >/dev/null 2>&1; then
+            cabbage validate --all
+          else
+            echo "Error: cabbage CLI not found. Expected a vendored .cabbage/tooling or an installed 'cabbage' command." >&2
+            exit 1
+          fi
+
+      - name: Validate PR Workflow & Doc Binding
+        if: github.event_name == 'pull_request'
+        run: |
+          if [ -d ".cabbage/tooling" ]; then
+            export PYTHONPATH=".cabbage/tooling${PYTHONPATH:+:$PYTHONPATH}"
+            python -m cabbage_cli ci --base origin/${{ github.base_ref }}
+          elif command -v cabbage >/dev/null 2>&1; then
+            cabbage ci --base origin/${{ github.base_ref }}
+          else
+            echo "Error: cabbage CLI not found. Expected a vendored .cabbage/tooling or an installed 'cabbage' command." >&2
+            exit 1
+          fi
+
+      - name: Set up pnpm
+        if: ${{ hashFiles('docs/package.json') != '' }}
+        uses: pnpm/action-setup@v4
+        with:
+          version: 10
+
+      - name: Set up Node.js
+        if: ${{ hashFiles('docs/package.json') != '' }}
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: 'pnpm'
+          cache-dependency-path: 'docs/pnpm-lock.yaml'
+
+      - name: Install documentation dependencies
+        if: ${{ hashFiles('docs/package.json') != '' }}
+        working-directory: docs
+        run: pnpm install --frozen-lockfile
+
+      - name: Build documentation site
+        if: ${{ hashFiles('docs/package.json') != '' }}
+        working-directory: docs
+        run: pnpm run build
+
+      - name: Upload Pages artifact
+        if: ${{ hashFiles('docs/package.json') != '' && github.event_name == 'push' && (github.ref == 'refs/heads/master' || github.ref == 'refs/heads/main') }}
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: docs/.vitepress/dist
+
+  deploy-pages:
+    name: Deploy to GitHub Pages
+    if: github.event_name == 'push' && (github.ref == 'refs/heads/master' || github.ref == 'refs/heads/main')
+    needs: validate-and-test
+    runs-on: ubuntu-latest
+    permissions:
+      pages: write
+      id-token: write
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

package/vendor/cabbage/cabbage_cli/assets/templates/adr.md

@@ -0,0 +1,47 @@
+---
+change: {{CHANGE_ID}}
+cabbage_stage: {{STAGE_ID}}
+change_type: {{CHANGE_TYPE}}
+---
+
+<!-- Replace every marked prompt before verifying this stage. -->
+
+# Status
+
+<!-- CABBAGE: Set Proposed, Accepted, Superseded, or Deprecated, with the decision date and owners. -->
+
+# Context
+
+<!-- CABBAGE: Describe the forces, constraints, and architectural problem that require a decision. -->
+
+# Decision Drivers
+
+- <!-- CABBAGE: List a criterion used to compare options. -->
+
+# Considered Options
+
+| Option | Benefits | Drawbacks | Outcome |
+|---|---|---|---|
+| <!-- CABBAGE: Name an option, including the status quo. --> | <!-- CABBAGE: List the benefits. --> | <!-- CABBAGE: List costs and risks. --> | <!-- CABBAGE: State why it was selected or rejected. --> |
+
+# Decision
+
+<!-- CABBAGE: State the chosen option and the boundaries of the decision. -->
+
+# Consequences
+
+## Positive
+
+- <!-- CABBAGE: Record an expected benefit. -->
+
+## Negative
+
+- <!-- CABBAGE: Record a cost, constraint, or accepted trade-off. -->
+
+## Risks
+
+- <!-- CABBAGE: Record a residual risk and mitigation. -->
+
+# Validation
+
+<!-- CABBAGE: Define how and when the decision will be reviewed or measured. -->

package/vendor/cabbage/cabbage_cli/assets/templates/api-design.md

@@ -0,0 +1,45 @@
+---
+change: {{CHANGE_ID}}
+cabbage_stage: {{STAGE_ID}}
+change_type: {{CHANGE_TYPE}}
+---
+
+<!-- Replace every marked prompt before verifying this stage. Use N/A with a reason when a section does not apply. -->
+
+# Overview
+
+<!-- CABBAGE: Identify the API purpose, protocol, owners, and consumers. -->
+
+# Contract
+
+## Operations
+
+| Method or event | Path or topic | Purpose | Authentication | Idempotency |
+|---|---|---|---|---|
+| <!-- CABBAGE: Name the method or event. --> | <!-- CABBAGE: Provide the path or topic. --> | <!-- CABBAGE: Describe the operation. --> | <!-- CABBAGE: State the required identity and permission. --> | <!-- CABBAGE: Describe retry and deduplication behavior. --> |
+
+## Inputs and Outputs
+
+| Name | Location | Type | Required | Validation or semantics |
+|---|---|---|---|---|
+| <!-- CABBAGE: Name a field. --> | <!-- CABBAGE: Path, query, header, or body. --> | <!-- CABBAGE: State the type. --> | <!-- CABBAGE: Yes or No. --> | <!-- CABBAGE: State constraints and meaning. --> |
+
+<!-- CABBAGE: Provide representative request, response, or event examples without secrets. -->
+
+# Error Model
+
+| Code or condition | Meaning | Client action | Retryable |
+|---|---|---|---|
+| <!-- CABBAGE: Name an error. --> | <!-- CABBAGE: Explain the failure. --> | <!-- CABBAGE: Describe recovery. --> | <!-- CABBAGE: Yes or No, with policy. --> |
+
+# Compatibility
+
+<!-- CABBAGE: Describe versioning, backward compatibility, deprecation, and consumer migration. -->
+
+# Security
+
+<!-- CABBAGE: Describe authorization, input validation, sensitive fields, rate limits, and abuse controls. -->
+
+# Observability
+
+<!-- CABBAGE: Define logs, metrics, traces, audit events, SLOs, and alerts for the contract. -->

package/vendor/cabbage/cabbage_cli/assets/templates/change-record.md

@@ -0,0 +1,21 @@
+---
+change: {{CHANGE_ID}}
+cabbage_stage: {{STAGE_ID}}
+change_type: {{CHANGE_TYPE}}
+---
+
+# Goal
+
+<!-- CABBAGE: Describe the goal or reproduced problem, scope, and observable acceptance criteria. -->
+
+# Design
+
+<!-- CABBAGE: Describe the minimal change and risks. Before implementation, declare architecture/API/database/security/design/RFC/high-risk deployment impacts with cabbage impact. -->
+
+# Tasks
+
+- [ ] <!-- CABBAGE: Implement the change and cover the affected behavior with tests. -->
+
+# Verification
+
+<!-- CABBAGE: Record exact commands and actual results. For a bugfix include the failing reproduction and passing regression. -->

package/vendor/cabbage/cabbage_cli/assets/templates/database-design.md

@@ -0,0 +1,37 @@
+---
+change: {{CHANGE_ID}}
+cabbage_stage: {{STAGE_ID}}
+change_type: {{CHANGE_TYPE}}
+---
+
+<!-- Replace every marked prompt before verifying this stage. Use N/A with a reason when a section does not apply. -->
+
+# Summary
+
+<!-- CABBAGE: Describe the data change, affected stores, ownership, and expected scale. -->
+
+# Schema
+
+| Object and field | Type | Nullable | Default | Constraint or index | Rationale |
+|---|---|---|---|---|---|
+| <!-- CABBAGE: Name the table, collection, and field. --> | <!-- CABBAGE: State the type. --> | <!-- CABBAGE: Yes or No. --> | <!-- CABBAGE: State the default. --> | <!-- CABBAGE: Describe keys, checks, or indexes. --> | <!-- CABBAGE: Explain the design choice. --> |
+
+<!-- CABBAGE: Record invariants, relationships, retention, and ownership rules. -->
+
+# Migration
+
+| Phase | Operation | Batching or lock risk | Verification | Owner |
+|---|---|---|---|---|
+| <!-- CABBAGE: Name expand, backfill, switch, or contract phase. --> | <!-- CABBAGE: Describe the operation. --> | <!-- CABBAGE: Describe load, duration, and concurrency risk. --> | <!-- CABBAGE: Define pass criteria. --> | <!-- CABBAGE: Name the owner. --> |
+
+# Data Verification
+
+<!-- CABBAGE: Define row counts, checksums, invariants, reconciliation, and post-migration sampling. -->
+
+# Compatibility and Operations
+
+<!-- CABBAGE: Describe mixed-version behavior, query performance, capacity, replication, backups, and observability. -->
+
+# Rollback
+
+<!-- CABBAGE: Define rollback triggers, ordering, recovery commands, and irreversible data impact. -->

package/vendor/cabbage/cabbage_cli/assets/templates/generic.md

@@ -0,0 +1,20 @@
+---
+change: {{CHANGE_ID}}
+cabbage_stage: {{STAGE_ID}}
+change_type: {{CHANGE_TYPE}}
+---
+
+<!-- Replace every marked prompt before verifying this stage. -->
+
+# Summary
+
+<!-- CABBAGE: State the artifact's purpose, audience, and expected outcome. -->
+
+# Content
+
+<!-- CABBAGE: Provide the information required by this workflow stage. -->
+
+# Decisions and Follow-up
+
+- Decision: <!-- CABBAGE: Record a decision or state N/A. -->
+- Follow-up: <!-- CABBAGE: Record an owner and due date or state N/A. -->

package/vendor/cabbage/cabbage_cli/assets/templates/impact.md

@@ -0,0 +1,41 @@
+---
+change: {{CHANGE_ID}}
+cabbage_stage: {{STAGE_ID}}
+change_type: {{CHANGE_TYPE}}
+---
+
+<!-- Replace every marked prompt before verifying this stage. Keep the matrix aligned with change.yaml. -->
+
+# Change Summary
+
+<!-- CABBAGE: Summarize what changes and which users, systems, or teams are affected. -->
+
+# Impact Matrix
+
+| Area | Impact | Notes |
+|---|---|---|
+| Product | No | |
+| Design | No | |
+| Architecture | No | |
+| RFC | No | |
+| API | No | |
+| Database | No | |
+| Security | No | |
+| Testing | Yes | |
+| Deployment | No | |
+| Operations | No | |
+| Performance | No | |
+
+# Impact Details
+
+<!-- CABBAGE: For each area marked Yes, describe affected components, consumers, data, and operational processes. -->
+
+# Risks
+
+| Risk | Likelihood | Impact | Mitigation | Owner |
+|---|---|---|---|---|
+| <!-- CABBAGE: Describe a material risk. --> | <!-- CABBAGE: Low, Medium, or High. --> | <!-- CABBAGE: Describe the consequence. --> | <!-- CABBAGE: Describe prevention or recovery. --> | <!-- CABBAGE: Name the accountable owner. --> |
+
+# Documentation Updates
+
+- <!-- CABBAGE: List current-state documents, runbooks, API references, or release notes to update. -->

package/vendor/cabbage/cabbage_cli/assets/templates/incident.md

@@ -0,0 +1,48 @@
+---
+change: {{CHANGE_ID}}
+cabbage_stage: {{STAGE_ID}}
+change_type: {{CHANGE_TYPE}}
+---
+
+<!-- Replace every marked prompt before verifying this stage. Use UTC or include the timezone for every timestamp. -->
+
+# Incident Metadata
+
+| Field | Value |
+|---|---|
+| Severity | <!-- CABBAGE: State the severity level. --> |
+| Status | <!-- CABBAGE: Investigating, Mitigated, Resolved, or Monitoring. --> |
+| Started / Detected / Resolved | <!-- CABBAGE: Record timestamps and timezone. --> |
+| Incident commander | <!-- CABBAGE: Name the accountable responder. --> |
+
+# Impact
+
+<!-- CABBAGE: Quantify affected users, duration, regions, features, data, revenue, and SLO or SLA impact. -->
+
+# Detection
+
+<!-- CABBAGE: Describe the first signal, detection delay, and why existing alerts did or did not work. -->
+
+# Timeline
+
+| Time | Event or observation | Action and owner |
+|---|---|---|
+| <!-- CABBAGE: Record a timestamp. --> | <!-- CABBAGE: Record a material event. --> | <!-- CABBAGE: Record the response and actor. --> |
+
+# Mitigation
+
+## Containment
+
+<!-- CABBAGE: Describe how impact was stopped or limited. -->
+
+## Recovery
+
+<!-- CABBAGE: Describe restoration steps and any remaining degraded behavior. -->
+
+# Recovery Verification
+
+<!-- CABBAGE: Record the metrics, checks, and observation window that prove recovery. -->
+
+# Communications
+
+<!-- CABBAGE: Record customer, stakeholder, support, and status-page updates with timestamps. -->

package/vendor/cabbage/cabbage_cli/assets/templates/postmortem.md

@@ -0,0 +1,43 @@
+---
+change: {{CHANGE_ID}}
+cabbage_stage: {{STAGE_ID}}
+change_type: {{CHANGE_TYPE}}
+---
+
+<!-- Replace every marked prompt before verifying this stage. Keep the analysis blameless and evidence based. -->
+
+# Summary
+
+<!-- CABBAGE: Summarize what happened, the duration, resolution, and principal lesson. -->
+
+# Impact and Detection
+
+<!-- CABBAGE: Quantify impact and explain how the incident was detected, including detection gaps. -->
+
+# Root Cause
+
+<!-- CABBAGE: State the causal chain with supporting evidence; distinguish the trigger from the root cause. -->
+
+# Contributing Factors
+
+- <!-- CABBAGE: Record a systemic condition that increased likelihood, impact, or recovery time. -->
+
+# Response Assessment
+
+## What Went Well
+
+- <!-- CABBAGE: Record an effective safeguard or response action. -->
+
+## What Went Poorly
+
+- <!-- CABBAGE: Record a response or process gap. -->
+
+# Corrective Actions
+
+| Action | Type | Owner | Due date | Verification | Status |
+|---|---|---|---|---|---|
+| <!-- CABBAGE: Define a specific preventive or detective action. --> | <!-- CABBAGE: Prevent, Detect, or Mitigate. --> | <!-- CABBAGE: Name one owner. --> | <!-- CABBAGE: Set a date. --> | <!-- CABBAGE: Define evidence of completion. --> | Open |
+
+# Lessons Learned
+
+<!-- CABBAGE: Record reusable technical or organizational learning and where it will be shared. -->

package/vendor/cabbage/cabbage_cli/assets/templates/prd.md

@@ -0,0 +1,71 @@
+---
+change: {{CHANGE_ID}}
+cabbage_stage: {{STAGE_ID}}
+change_type: {{CHANGE_TYPE}}
+---
+
+<!-- Replace every marked prompt before verifying this stage. Use N/A with a reason when a section does not apply. -->
+
+# Goal
+
+<!-- CABBAGE: State the user or business problem, the desired outcome, and why it matters now. -->
+
+## Grill-Me Alignment Summary
+
+- **Core Problem & Value**: <!-- CABBAGE: Summarize the clarified business intent and primary value hypothesis from pre-flight grilling. -->
+- **Assumptions Validated**: <!-- CABBAGE: Record validated assumptions and eliminated ambiguities. -->
+
+# Users and Use Cases
+
+| User or actor | Need | Primary use case |
+|---|---|---|
+| <!-- CABBAGE: Identify the affected user or system. --> | <!-- CABBAGE: Describe the need. --> | <!-- CABBAGE: Describe the observable workflow. --> |
+
+# Scope
+
+## In Scope
+
+- <!-- CABBAGE: List behavior delivered by this change. -->
+
+## Out of Scope
+
+- <!-- CABBAGE: List adjacent behavior intentionally excluded. -->
+
+## Decision Boundaries
+
+- **AI Autonomous Decisions**: <!-- CABBAGE: Technical details, internal naming, local refactoring, and test fixtures decided directly by AI. -->
+- **Human Gate Decisions**: <!-- CABBAGE: Business rules, breaking interface/data model changes, scope expansion, and domain trade-offs requiring explicit human approval. -->
+
+# Requirements
+
+| ID | Requirement (SHALL/MUST) | Priority | Rationale |
+|---|---|---|---|
+| R-1 | <!-- CABBAGE: Write a testable requirement using SHALL/MUST. --> | Must | <!-- CABBAGE: Explain why it is needed. --> |
+
+# Acceptance Criteria
+
+### Scenario 1: <!-- CABBAGE: Scenario title -->
+- **GIVEN**: <!-- CABBAGE: Initial context / precondition -->
+- **WHEN**: <!-- CABBAGE: Action or event triggered -->
+- **THEN**: <!-- CABBAGE: Observable expected outcome -->
+- [ ] <!-- CABBAGE: Acceptance verification checkbox -->
+
+# Success Metrics
+
+| Metric | Baseline | Target | Measurement window |
+|---|---|---|---|
+| <!-- CABBAGE: Name the outcome metric. --> | <!-- CABBAGE: Record the current value. --> | <!-- CABBAGE: Record the target value. --> | <!-- CABBAGE: Define when it is evaluated. --> |
+
+# Dependencies and Constraints
+
+- <!-- CABBAGE: Record external dependencies, policy constraints, deadlines, or compatibility requirements. -->
+
+# Risks
+
+| Risk | Impact | Mitigation |
+|---|---|---|
+| <!-- CABBAGE: Describe a product or delivery risk. --> | <!-- CABBAGE: Describe the consequence. --> | <!-- CABBAGE: Describe the mitigation. --> |
+
+# Open Questions
+
+- <!-- CABBAGE: Record unresolved decisions and an owner, or state N/A. -->

package/vendor/cabbage/cabbage_cli/assets/templates/release-plan.md

@@ -0,0 +1,45 @@
+---
+change: {{CHANGE_ID}}
+cabbage_stage: {{STAGE_ID}}
+change_type: {{CHANGE_TYPE}}
+---
+
+<!-- Replace every marked prompt before verifying this stage. Use N/A with a reason when a section does not apply. -->
+
+# Release Summary
+
+<!-- CABBAGE: Identify the release, affected services or clients, release window, and accountable owner. -->
+
+# Preconditions
+
+- [ ] <!-- CABBAGE: List an approval, dependency, backup, migration, capacity, or compatibility prerequisite. -->
+
+# Deployment
+
+| Order | Action | Owner | Success signal |
+|---|---|---|---|
+| 1 | <!-- CABBAGE: Describe a concrete deployment step. --> | <!-- CABBAGE: Name the owner. --> | <!-- CABBAGE: Define the expected signal. --> |
+
+# Rollback
+
+## Triggers
+
+- <!-- CABBAGE: Define a measurable rollback trigger. -->
+
+## Steps
+
+1. <!-- CABBAGE: Describe rollback ordering, ownership, and data handling. -->
+
+# Verification
+
+| Check | Method | Expected result | Owner |
+|---|---|---|---|
+| <!-- CABBAGE: Name a functional or operational check. --> | <!-- CABBAGE: Provide a command, dashboard, or procedure. --> | <!-- CABBAGE: Define pass criteria. --> | <!-- CABBAGE: Name the verifier. --> |
+
+# Monitoring
+
+<!-- CABBAGE: List dashboards, alerts, logs, observation duration, and escalation thresholds. -->
+
+# Communication
+
+<!-- CABBAGE: Describe stakeholder notification, support readiness, status updates, and release notes. -->

package/vendor/cabbage/cabbage_cli/assets/templates/rfc.md

@@ -0,0 +1,44 @@
+---
+change: {{CHANGE_ID}}
+cabbage_stage: {{STAGE_ID}}
+change_type: {{CHANGE_TYPE}}
+---
+
+<!-- Replace every marked prompt before verifying this stage. -->
+
+# Summary
+
+<!-- CABBAGE: Summarize the proposed direction and decision requested from reviewers. -->
+
+# Problem
+
+<!-- CABBAGE: Describe the current problem, evidence, affected parties, and cost of doing nothing. -->
+
+# Goals and Non-goals
+
+- Goal: <!-- CABBAGE: State an outcome the proposal must achieve. -->
+- Non-goal: <!-- CABBAGE: State an adjacent concern intentionally excluded. -->
+
+# Proposal
+
+<!-- CABBAGE: Explain the approach, key components, boundaries, and operational model at decision level. -->
+
+# Alternatives
+
+| Option | Benefits | Costs and risks | Outcome |
+|---|---|---|---|
+| <!-- CABBAGE: Name an alternative, including the status quo. --> | <!-- CABBAGE: List advantages. --> | <!-- CABBAGE: List disadvantages. --> | <!-- CABBAGE: State why it is preferred or rejected. --> |
+
+# Compatibility and Migration
+
+<!-- CABBAGE: Describe consumer impact, transition phases, compatibility window, and deprecation. -->
+
+# Risks
+
+| Risk | Impact | Mitigation |
+|---|---|---|
+| <!-- CABBAGE: Describe a proposal risk. --> | <!-- CABBAGE: Describe the consequence. --> | <!-- CABBAGE: Describe mitigation or recovery. --> |
+
+# Open Questions
+
+- <!-- CABBAGE: Record an unresolved decision, owner, and target date. -->

package/vendor/cabbage/cabbage_cli/assets/templates/security-review.md

@@ -0,0 +1,35 @@
+---
+change: {{CHANGE_ID}}
+cabbage_stage: {{STAGE_ID}}
+change_type: {{CHANGE_TYPE}}
+---
+
+<!-- Replace every marked prompt before verifying this stage. -->
+
+# Scope and Assets
+
+| Asset or trust boundary | Sensitivity | Actor or owner |
+|---|---|---|
+| <!-- CABBAGE: Identify data, credentials, service, or boundary. --> | <!-- CABBAGE: State sensitivity and business impact. --> | <!-- CABBAGE: Name users, systems, and owner. --> |
+
+# Threats
+
+| ID | Threat or abuse case | Preconditions | Impact | Likelihood |
+|---|---|---|---|---|
+| S-1 | <!-- CABBAGE: Describe a credible threat. --> | <!-- CABBAGE: State what enables it. --> | <!-- CABBAGE: Describe the consequence. --> | <!-- CABBAGE: Low, Medium, or High. --> |
+
+# Controls
+
+| Threat ID | Preventive or detective control | Verification evidence | Owner |
+|---|---|---|---|
+| S-1 | <!-- CABBAGE: Describe authorization, validation, secrets, audit, or another control. --> | <!-- CABBAGE: Name a test, scan, log, or review. --> | <!-- CABBAGE: Name the owner. --> |
+
+# Residual Risks
+
+| Risk | Reason accepted | Approver | Review date |
+|---|---|---|---|
+| <!-- CABBAGE: Describe remaining exposure, or state N/A. --> | <!-- CABBAGE: Explain the trade-off. --> | <!-- CABBAGE: Name the risk owner. --> | <!-- CABBAGE: Set the review date. --> |
+
+# Verification
+
+- <!-- CABBAGE: List required security tests, privacy checks, and release-blocking evidence. -->