releasehx 0.1.2 → 0.2.0

data/lib/releasehx/mcp/assets/agent-config-guide.md

@@ -137,7 +137,7 @@ Use `releasehx://config/schema` when:
 ## Potentially unintuitive principles
 
 - **“Frontmatter” is controlled in two places (toggle vs template).**  
-  If you’re trying to *turn frontmatter on/off*, look under `modes.*_frontmatter`. If you’re trying to *change what frontmatter contains*, look under `templates.*_frontmatter` (Markdown/AsciiDoc/HTML each have their own). Also note `modes.wrapped` affects HTML wrapping, which can look like a frontmatter problem when it’s really wrapping/boilerplate.
+  If you're trying to *turn frontmatter on/off*, look under `modes.*_frontmatter`. If you're trying to *change what frontmatter contains*, look under `templates.*_frontmatter` (Markdown/AsciiDoc/HTML each have their own). Also note `modes.html_wrap` affects HTML wrapping, which can look like a frontmatter problem when it's really wrapping/boilerplate.
 
 - **Links require both a template and an enable switch.**  
   Defining URL templates under `links.web.href` / `links.git.href` does nothing by itself. You must also enable display under `history.items.show_issue_links` / `history.items.show_git_links` (or the per-section overrides under changelog/notes items, if present). If a user says “I set the link template but no links appear,” check the `history.*items*` flags.

data/lib/releasehx/mcp/assets/config-def.yml

@@ -203,12 +203,59 @@ properties:
           The origin markup format for notes.
           May be `markdown` or `asciidoc`.
         dflt: markdown
-      engine:
-        type: String
+      engines:
         desc: |
-          The markup converter to use for the issues.
-          Defaults to `asciidoctor` for AsciiDoc and `redcarpet` for Markdown.
-          Options include `asciidoctor`, `redcarpet`, `commonmarker`, `kramdown`, or `pandoc`.
+          Specifies the conversion engines to use when enriching to various output formats.
+          
+          These settings determine which tool processes the conversion from draft formats to rich output.
+          Intelligent defaults are applied based on source format when engines are not explicitly configured.
+        properties:
+          html:
+            type: String
+            desc: |
+              Engine for converting to HTML format.
+              
+              Valid engines:
+              
+              [horizontal]
+              `asciidoctor-html5`:: Standard Asciidoctor HTML5 backend (nested div structure)
+              `asciidoctor-html5s`:: Semantic HTML5 backend (cleaner section-based markup)
+              `kramdown`:: Kramdown Markdown converter (for Markdown sources)
+              `pandoc`:: Universal document converter (if available)
+              
+              When not specified, intelligent defaults apply:
+              
+              - AsciiDoc → HTML: `asciidoctor-html5s` (semantic HTML5)
+              - Markdown → HTML: `kramdown`
+              - RHYML → HTML: Liquid templates (no engine needed)
+            docs: |
+              The html5s backend produces cleaner, more semantic HTML with `<section>` elements
+              instead of nested `<div class="sect1"><div class="sectionbody">` structures.
+              
+              This is particularly useful when you want to apply custom CSS or when generating
+              HTML that will be further processed or embedded in other systems.
+              
+              For backwards compatibility or when you need the traditional Asciidoctor structure,
+              use `asciidoctor-html5`.
+          pdf:
+            type: String
+            desc: |
+              Engine for converting to PDF format.
+              
+              Valid engines:
+              
+              [horizontal]
+              `asciidoctor-pdf`:: Asciidoctor PDF converter (default for AsciiDoc)
+              `asciidoctor-web-pdf`:: Web-based PDF converter using headless Chrome
+              `pandoc`:: Universal document converter (if available)
+              
+              When not specified, intelligent defaults apply:
+              
+              - AsciiDoc → PDF: `asciidoctor-pdf`
+              - Markdown → PDF: `pandoc` (if available)
+            docs: |
+              The default `asciidoctor-pdf` engine provides excellent typography and layout
+              for technical documentation with support for themes, fonts, and advanced formatting.
 
   extensions:
     desc: Default file extensions.
@@ -837,7 +884,7 @@ properties:
     desc: |
       Default settings for `rhx` command executions.
     properties:
-      wrapped:
+      html_wrap:
         type: Boolean
         desc: |
           Include (or exclude) head, header, and footer elements when enriching to HTML.
@@ -862,6 +909,7 @@ properties:
           Include frontmatter in AsciiDoc drafts.
 
           Uses the `templates.asciidoc_frontmatter` template.
+        dflt: false
       fetch:
         type: String
         desc: |
@@ -1043,6 +1091,74 @@ properties:
 
           It may include `{{ title }}`, `{{ version }}`, `{{ date }}`, as well as any `vars`-scoped variables as you pass in.
         dflt: *markdown_frontmatter_tplt
+      html_framework:
+        type: String
+        desc: |
+          The HTML framework to use when enriching to HTML.
+
+          Valid entries:
+          
+          [horizontal]
+          `bare`:: minimal HTML structure
+          `bootstrap4`:: Bootstrap 4 framework
+          `bootstrap5`:: Bootstrap 5 framework
+        dflt: bare
+      styling:
+        desc: |
+          Configuration options for HTML styling and CSS framework integration.
+        properties:
+          mode:
+            type: String
+            desc: |
+              The HTML styling approach to use when generating wrapped HTML output.
+
+              Valid options:
+
+              * `minimal` -- Basic semantic HTML with minimal inline styles
+              * `embedded` -- Include comprehensive CSS in `<style>` block 
+              * `external` -- Reference external stylesheet via `<link>` tag
+              * `framework` -- Use configured CSS framework only (Bootstrap, etc.)
+
+              When `mode: framework`, styling relies entirely on the configured CSS framework.
+              When `mode: embedded`, CSS is included inline for standalone HTML files.
+              When `mode: external`, a custom CSS file must be provided via `css_url`.
+            dflt: framework
+          theme:
+            type: String
+            desc: |
+              The visual theme variant to apply to HTML output.
+
+              Built-in themes:
+
+              * `default` -- Standard professional appearance
+              * `compact` -- Reduced spacing and condensed layout
+              * `detailed` -- Enhanced metadata display with expanded information
+
+              Theme selection affects spacing, typography, and metadata prominence.
+            dflt: default
+          embed_css:
+            type: Boolean
+            desc: |
+              Include comprehensive CSS directly in the HTML `<style>` block.
+
+              When enabled, generates standalone HTML files that display correctly
+              without external dependencies. CSS includes framework customizations,
+              responsive design rules, and print optimizations.
+
+              Automatically enabled when `mode: embedded`.
+            dflt: false
+          css_url:
+            type: String
+            desc: |
+              URL or path to external CSS stylesheet for custom styling.
+
+              When `mode: external`, this stylesheet is linked via `<link rel="stylesheet">`.
+              Can be a relative path, absolute URL, or CDN link.
+
+              Example: `assets/custom-releasehx.css` or `https://example.com/styles.css`
+
+              When provided, framework CSS and embedded CSS are disabled.
+            dflt: null
       items:
         desc: |
           Settings pertaining to displayed items across Changelog and Release Notes sections.

data/lib/releasehx/mcp/assets/config-reference.adoc

@@ -438,18 +438,80 @@ default;;
 path;; `xref:conf_ppty_conversions_markup[config.conversions.markup]`
 --
 
-[[conf_ppty_conversions_engine,config.conversions.engine]]
-conversions.engine:::
+[[conf_ppty_conversions_engines,config.conversions.engines]]
+conversions.engines:::
 +
 --
-The markup converter to use for the issues.
-Defaults to `asciidoctor` for AsciiDoc and `redcarpet` for Markdown.
-Options include `asciidoctor`, `redcarpet`, `commonmarker`, `kramdown`, or `pandoc`.
+Specifies the conversion engines to use when enriching to various output formats.
+
+These settings determine which tool processes the conversion from draft formats to rich output.
+Intelligent defaults are applied based on source format when engines are not explicitly configured.
+
+
+[horizontal]
+path;; `xref:conf_ppty_conversions_engines[config.conversions.engines]`
+--
+
+[[conf_ppty_conversions_engines_html,config.conversions.engines.html]]
+conversions.engines.html::::
++
+--
+Engine for converting to HTML format.
+
+Valid engines:
+
+[horizontal]
+`asciidoctor-html5`:: Standard Asciidoctor HTML5 backend (nested div structure)
+`asciidoctor-html5s`:: Semantic HTML5 backend (cleaner section-based markup)
+`kramdown`:: Kramdown Markdown converter (for Markdown sources)
+`pandoc`:: Universal document converter (if available)
+
+When not specified, intelligent defaults apply:
+
+- AsciiDoc → HTML: `asciidoctor-html5s` (semantic HTML5)
+- Markdown → HTML: `kramdown`
+- RHYML → HTML: Liquid templates (no engine needed)
+
+The html5s backend produces cleaner, more semantic HTML with `<section>` elements
+instead of nested `<div class="sect1"><div class="sectionbody">` structures.
+
+This is particularly useful when you want to apply custom CSS or when generating
+HTML that will be further processed or embedded in other systems.
+
+For backwards compatibility or when you need the traditional Asciidoctor structure,
+use `asciidoctor-html5`.
 
 
 [horizontal]
 type;; String
-path;; `xref:conf_ppty_conversions_engine[config.conversions.engine]`
+path;; `xref:conf_ppty_conversions_engines_html[config.conversions.engines.html]`
+--
+
+[[conf_ppty_conversions_engines_pdf,config.conversions.engines.pdf]]
+conversions.engines.pdf::::
++
+--
+Engine for converting to PDF format.
+
+Valid engines:
+
+[horizontal]
+`asciidoctor-pdf`:: Asciidoctor PDF converter (default for AsciiDoc)
+`asciidoctor-web-pdf`:: Web-based PDF converter using headless Chrome
+`pandoc`:: Universal document converter (if available)
+
+When not specified, intelligent defaults apply:
+
+- AsciiDoc → PDF: `asciidoctor-pdf`
+- Markdown → PDF: `pandoc` (if available)
+
+The default `asciidoctor-pdf` engine provides excellent typography and layout
+for technical documentation with support for themes, fonts, and advanced formatting.
+
+
+[horizontal]
+type;; String
+path;; `xref:conf_ppty_conversions_engines_pdf[config.conversions.engines.pdf]`
 --
 
 [[conf_ppty_extensions,config.extensions]]
@@ -2497,8 +2559,8 @@ Default settings for `rhx` command executions.
 path;; `xref:conf_ppty_modes[config.modes]`
 --
 
-[[conf_ppty_modes_wrapped,config.modes.wrapped]]
-modes.wrapped:::
+[[conf_ppty_modes_html_wrap,config.modes.html_wrap]]
+modes.html_wrap:::
 +
 --
 Include (or exclude) head, header, and footer elements when enriching to HTML.
@@ -2509,7 +2571,7 @@ type;; Boolean
 default;;
 +
 `+++false+++`
-path;; `xref:conf_ppty_modes_wrapped[config.modes.wrapped]`
+path;; `xref:conf_ppty_modes_html_wrap[config.modes.html_wrap]`
 --
 
 [[conf_ppty_modes_html_frontmatter,config.modes.html_frontmatter]]
@@ -2557,6 +2619,9 @@ Uses the `templates.asciidoc_frontmatter` template.
 
 [horizontal]
 type;; Boolean
+default;;
++
+`+++false+++`
 path;; `xref:conf_ppty_modes_asciidoc_frontmatter[config.modes.asciidoc_frontmatter]`
 --
 
@@ -2871,6 +2936,128 @@ date: {{ release.date }}
 path;; `xref:conf_ppty_history_html_frontmatter[config.history.html_frontmatter]`
 --
 
+[[conf_ppty_history_html_framework,config.history.html_framework]]
+history.html_framework:::
++
+--
+The HTML framework to use when enriching to HTML.
+
+Valid entries:
+
+[horizontal]
+`bare`:: minimal HTML structure
+`bootstrap4`:: Bootstrap 4 framework
+`bootstrap5`:: Bootstrap 5 framework
+
+
+[horizontal]
+type;; String
+default;;
++
+`+++bare+++`
+path;; `xref:conf_ppty_history_html_framework[config.history.html_framework]`
+--
+
+[[conf_ppty_history_styling,config.history.styling]]
+history.styling:::
++
+--
+Configuration options for HTML styling and CSS framework integration.
+
+
+[horizontal]
+path;; `xref:conf_ppty_history_styling[config.history.styling]`
+--
+
+[[conf_ppty_history_styling_mode,config.history.styling.mode]]
+history.styling.mode::::
++
+--
+The HTML styling approach to use when generating wrapped HTML output.
+
+Valid options:
+
+* `minimal` -- Basic semantic HTML with minimal inline styles
+* `embedded` -- Include comprehensive CSS in `<style>` block 
+* `external` -- Reference external stylesheet via `<link>` tag
+* `framework` -- Use configured CSS framework only (Bootstrap, etc.)
+
+When `mode: framework`, styling relies entirely on the configured CSS framework.
+When `mode: embedded`, CSS is included inline for standalone HTML files.
+When `mode: external`, a custom CSS file must be provided via `css_url`.
+
+
+[horizontal]
+type;; String
+default;;
++
+`+++framework+++`
+path;; `xref:conf_ppty_history_styling_mode[config.history.styling.mode]`
+--
+
+[[conf_ppty_history_styling_theme,config.history.styling.theme]]
+history.styling.theme::::
++
+--
+The visual theme variant to apply to HTML output.
+
+Built-in themes:
+
+* `default` -- Standard professional appearance
+* `compact` -- Reduced spacing and condensed layout
+* `detailed` -- Enhanced metadata display with expanded information
+
+Theme selection affects spacing, typography, and metadata prominence.
+
+
+[horizontal]
+type;; String
+default;;
++
+`+++default+++`
+path;; `xref:conf_ppty_history_styling_theme[config.history.styling.theme]`
+--
+
+[[conf_ppty_history_styling_embed_css,config.history.styling.embed_css]]
+history.styling.embed_css::::
++
+--
+Include comprehensive CSS directly in the HTML `<style>` block.
+
+When enabled, generates standalone HTML files that display correctly
+without external dependencies. CSS includes framework customizations,
+responsive design rules, and print optimizations.
+
+Automatically enabled when `mode: embedded`.
+
+
+[horizontal]
+type;; Boolean
+default;;
++
+`+++false+++`
+path;; `xref:conf_ppty_history_styling_embed_css[config.history.styling.embed_css]`
+--
+
+[[conf_ppty_history_styling_css_url,config.history.styling.css_url]]
+history.styling.css_url::::
++
+--
+URL or path to external CSS stylesheet for custom styling.
+
+When `mode: external`, this stylesheet is linked via `<link rel="stylesheet">`.
+Can be a relative path, absolute URL, or CDN link.
+
+Example: `assets/custom-releasehx.css` or `https://example.com/styles.css`
+
+When provided, framework CSS and embedded CSS are disabled.
+
+
+[horizontal]
+type;; String
+path;; `xref:conf_ppty_history_styling_css_url[config.history.styling.css_url]`
+--
+
 [[conf_ppty_history_items,config.history.items]]
 history.items:::
 +
@@ -4101,4 +4288,4 @@ default;;
 +
 `+++false+++`
 path;; `xref:conf_ppty_notes_items_show_auths_label[config.notes.items.show_auths_label]`
---
+--

data/lib/releasehx/mcp/assets/config-reference.json

@@ -155,10 +155,23 @@
           "type": "String",
           "default": "markdown"
         },
-        "engine": {
-          "path": "conversions.engine",
-          "desc": "The markup converter to use for the issues.\nDefaults to `asciidoctor` for AsciiDoc and `redcarpet` for Markdown.\nOptions include `asciidoctor`, `redcarpet`, `commonmarker`, `kramdown`, or `pandoc`.\n",
-          "type": "String"
+        "engines": {
+          "path": "conversions.engines",
+          "desc": "Specifies the conversion engines to use when enriching to various output formats.\n\nThese settings determine which tool processes the conversion from draft formats to rich output.\nIntelligent defaults are applied based on source format when engines are not explicitly configured.\n",
+          "properties": {
+            "html": {
+              "path": "conversions.engines.html",
+              "desc": "Engine for converting to HTML format.\n\nValid engines:\n\n[horizontal]\n`asciidoctor-html5`:: Standard Asciidoctor HTML5 backend (nested div structure)\n`asciidoctor-html5s`:: Semantic HTML5 backend (cleaner section-based markup)\n`kramdown`:: Kramdown Markdown converter (for Markdown sources)\n`pandoc`:: Universal document converter (if available)\n\nWhen not specified, intelligent defaults apply:\n\n- AsciiDoc → HTML: `asciidoctor-html5s` (semantic HTML5)\n- Markdown → HTML: `kramdown`\n- RHYML → HTML: Liquid templates (no engine needed)\n",
+              "docs": "The html5s backend produces cleaner, more semantic HTML with `<section>` elements\ninstead of nested `<div class=\"sect1\"><div class=\"sectionbody\">` structures.\n\nThis is particularly useful when you want to apply custom CSS or when generating\nHTML that will be further processed or embedded in other systems.\n\nFor backwards compatibility or when you need the traditional Asciidoctor structure,\nuse `asciidoctor-html5`.\n",
+              "type": "String"
+            },
+            "pdf": {
+              "path": "conversions.engines.pdf",
+              "desc": "Engine for converting to PDF format.\n\nValid engines:\n\n[horizontal]\n`asciidoctor-pdf`:: Asciidoctor PDF converter (default for AsciiDoc)\n`asciidoctor-web-pdf`:: Web-based PDF converter using headless Chrome\n`pandoc`:: Universal document converter (if available)\n\nWhen not specified, intelligent defaults apply:\n\n- AsciiDoc → PDF: `asciidoctor-pdf`\n- Markdown → PDF: `pandoc` (if available)\n",
+              "docs": "The default `asciidoctor-pdf` engine provides excellent typography and layout\nfor technical documentation with support for themes, fonts, and advanced formatting.\n",
+              "type": "String"
+            }
+          }
         }
       }
     },
@@ -996,8 +1009,8 @@
       "path": "modes",
       "desc": "Default settings for `rhx` command executions.\n",
       "properties": {
-        "wrapped": {
-          "path": "modes.wrapped",
+        "html_wrap": {
+          "path": "modes.html_wrap",
           "desc": "Include (or exclude) head, header, and footer elements when enriching to HTML.\n",
           "type": "Boolean",
           "default": false
@@ -1017,7 +1030,8 @@
         "asciidoc_frontmatter": {
           "path": "modes.asciidoc_frontmatter",
           "desc": "Include frontmatter in AsciiDoc drafts.\n\nUses the `templates.asciidoc_frontmatter` template.\n",
-          "type": "Boolean"
+          "type": "Boolean",
+          "default": false
         },
         "fetch": {
           "path": "modes.fetch",
@@ -1126,6 +1140,41 @@
           "type": "Liquid",
           "default": "---\ntitle: Release History for {{ release.code }}\nversion: {{ release.code }}\ndate: {{ release.date }}\n---\n"
         },
+        "html_framework": {
+          "path": "history.html_framework",
+          "desc": "The HTML framework to use when enriching to HTML.\n\nValid entries:\n\n[horizontal]\n`bare`:: minimal HTML structure\n`bootstrap4`:: Bootstrap 4 framework\n`bootstrap5`:: Bootstrap 5 framework\n",
+          "type": "String",
+          "default": "bare"
+        },
+        "styling": {
+          "path": "history.styling",
+          "desc": "Configuration options for HTML styling and CSS framework integration.\n",
+          "properties": {
+            "mode": {
+              "path": "history.styling.mode",
+              "desc": "The HTML styling approach to use when generating wrapped HTML output.\n\nValid options:\n\n* `minimal` -- Basic semantic HTML with minimal inline styles\n* `embedded` -- Include comprehensive CSS in `<style>` block \n* `external` -- Reference external stylesheet via `<link>` tag\n* `framework` -- Use configured CSS framework only (Bootstrap, etc.)\n\nWhen `mode: framework`, styling relies entirely on the configured CSS framework.\nWhen `mode: embedded`, CSS is included inline for standalone HTML files.\nWhen `mode: external`, a custom CSS file must be provided via `css_url`.\n",
+              "type": "String",
+              "default": "framework"
+            },
+            "theme": {
+              "path": "history.styling.theme",
+              "desc": "The visual theme variant to apply to HTML output.\n\nBuilt-in themes:\n\n* `default` -- Standard professional appearance\n* `compact` -- Reduced spacing and condensed layout\n* `detailed` -- Enhanced metadata display with expanded information\n\nTheme selection affects spacing, typography, and metadata prominence.\n",
+              "type": "String",
+              "default": "default"
+            },
+            "embed_css": {
+              "path": "history.styling.embed_css",
+              "desc": "Include comprehensive CSS directly in the HTML `<style>` block.\n\nWhen enabled, generates standalone HTML files that display correctly\nwithout external dependencies. CSS includes framework customizations,\nresponsive design rules, and print optimizations.\n\nAutomatically enabled when `mode: embedded`.\n",
+              "type": "Boolean",
+              "default": false
+            },
+            "css_url": {
+              "path": "history.styling.css_url",
+              "desc": "URL or path to external CSS stylesheet for custom styling.\n\nWhen `mode: external`, this stylesheet is linked via `<link rel=\"stylesheet\">`.\nCan be a relative path, absolute URL, or CDN link.\n\nExample: `assets/custom-releasehx.css` or `https://example.com/styles.css`\n\nWhen provided, framework CSS and embedded CSS are disabled.\n",
+              "type": "String"
+            }
+          }
+        },
         "items": {
           "path": "history.items",
           "desc": "Settings pertaining to displayed items across Changelog and Release Notes sections.\n\nMost of these settings can be defined separately for each section under <<conf_ppty_changelog_items>> and <<conf_ppty_notes_items>>.\nIf an identically named setting exists, it will override the primary designator defined in this `config.history.items` block.\n",

data/lib/releasehx/mcp/assets/sample-config.yml

@@ -25,7 +25,9 @@ conversions: # Details about content origination, as well as markup sources and
   note: issue_body # The source of the release notes content.
 #   note_custom_field:  # The name of the custom field to use for the release notes content.Liquid error: wrong number of arguments (given 3, expected 1..2)Liquid error: wrong number of arguments (given 3, expected 1..2)
   markup: markdown # The origin markup format for notes.
-#   engine:  # The markup converter to use for the issues.
+  engines: # Specifies the conversion engines to use when enriching to various output formats.
+#     html:  # Engine for converting to HTML format.
+#     pdf:  # Engine for converting to PDF format.
 extensions: # Default file extensions.
   markdown: md # File extension for Markdown drafts.
   asciidoc: adoc # File extension for AsciiDoc drafts.
@@ -72,7 +74,7 @@ tags: # Handling for tags, labels, or toggles associated with source Issues.
     - breaking
     - experimental
     - changelog
-  _exclude: # The list of tags that cause a change/issue to be excluded from the release history.
+  _exclude: [] # The list of tags that cause a change/issue to be excluded from the release history.
   highlight: # The tag, label, or toggle that indicates an issue is to be highlighted or prioritized in sorts.
     head: Highlights # How this tag will display as a grouping title.
     text: highlight # How this tag will display as a label.
@@ -163,10 +165,10 @@ paths: # The configuration for the paths to include in the release history listi
   mappings_dir: _mappings # The path to the directory containing user-defined API mappings.
   api_clients_dir: _apis # The path to the directory containing user-defined API client definitions.
 modes: # Default settings for rhx command executions.
-  wrapped: false # Include (or exclude) head, header, and footer elements when enriching to HTML.
+  html_wrap: false # Include (or exclude) head, header, and footer elements when enriching to HTML.
   html_frontmatter: true # Include frontmatter in the rendered HTML.
   markdown_frontmatter: false # Include frontmatter in Markdown drafts.
-#   asciidoc_frontmatter:  # Include frontmatter in AsciiDoc drafts.
+  asciidoc_frontmatter: false # Include frontmatter in AsciiDoc drafts.
   fetch: notes-only # What to fetch when gathering issues from API.
   remove_excess_lines: 1 # Reduces N+ consecutive blank lines to N lines.
 rhyml: # Settings related to RHYML data objects and documents.
@@ -178,6 +180,12 @@ rhyml: # Settings related to RHYML data objects and documents.
   pasterize_head: false # Whether to convert verbs in the head property to past tense when drafting.
 history: # Configurations for the overall document, when applicable.Liquid error: wrong number of arguments (given 3, expected 1..2)
   htag: h1 # The heading level (H1, H2, etc) for the release history header.Liquid error: wrong number of arguments (given 3, expected 1..2)Liquid error: wrong number of arguments (given 3, expected 1..2)Liquid error: wrong number of arguments (given 3, expected 1..2)
+  html_framework: bare # The HTML framework to use when enriching to HTML.
+  styling: # Configuration options for HTML styling and CSS framework integration.
+    mode: framework # The HTML styling approach to use when generating wrapped HTML output.
+    theme: default # The visual theme variant to apply to HTML output.
+    embed_css: false # Include comprehensive CSS directly in the HTML <style> block.
+#     css_url:  # URL or path to external CSS stylesheet for custom styling.
   items: # Settings pertaining to displayed items across Changelog and Release Notes sections.
     allow_redundant: false # Whether to allow duplicate entries in a given section, for instance across groups for part:group sorts where a change affects...
     show_issue_links: false # Whether to include web links in item metadata.
@@ -210,8 +218,7 @@ changelog: # The configuration for the changelog output.
   head: Changelog # The header for the changelog output.Liquid error: wrong number of arguments (given 3, expected 1..2)
   htag: h2 # The heading level (H1, H2, etc) for the changelog section header.
   spot: 2 # Where in the document to place the changelog (1 = top, 2 = bottom).
-  sort: # The sort order for the changelog output.
-    - part:grouping1
+  sort: [part:grouping1] # The sort order for the changelog output.
   items: # Settings that affect the frame/shape and arrangement of individual changelog entries.
     frame: unordered # The layout for the changelog entry display.
     allow_redundant: false # Whether to allow duplicate entries in a given section, for instance across groups for part:group sorts where a change affects...
@@ -248,4 +255,4 @@ notes: # The configuration for the Release Notes listing section.
     show_parts_label: false # Whether to show the parts label in the item metadata output.
     show_tags_label: false # Whether to show the tags label in the item metadata output.
     show_lead_label: false # Whether to show the lead label in the item metadata output.
-    show_auths_label: false # Whether to show the authors label in the item metadata output.
+    show_auths_label: false # Whether to show the authors label in the item metadata output.

data/lib/releasehx/mcp/server.rb

@@ -1,7 +1,6 @@
 # frozen_string_literal: true
 
 require 'json'
-require_relative '../../schemagraphy'
 require_relative '../../docopslab/mcp/server'
 require_relative 'manifest'
 require_relative 'resource_pack'