winter-super-cli 2026.5.15

package/resources/local/codex/plugins/cache/openai-primary-runtime/documents/26.505.10851/skills/documents/ooxml/comments.md

@@ -0,0 +1,37 @@
+# OOXML: Word comments (true comments)
+
+## Important reality
+**PDF/image rendering is not a reliable way to verify comments.** Comments often do not render at all in headless LibreOffice.
+
+If the task requires verifying comments, do a structural check.
+
+## Minimum wiring for a comment
+A comment requires three cooperating pieces:
+
+1) `word/comments.xml` exists and contains a `<w:comment w:id="...">` with the comment text.
+2) `word/document.xml` contains anchors:
+   - `<w:commentRangeStart w:id="..."/>`
+   - `<w:commentRangeEnd w:id="..."/>`
+   - a `<w:commentReference w:id="..."/>` in a run after the range
+3) Relationships + content-types:
+   - `word/_rels/document.xml.rels`: add a relationship of Type `http://schemas.openxmlformats.org/officeDocument/2006/relationships/comments` targeting `comments.xml`
+   - `[Content_Types].xml`: add an Override for `/word/comments.xml` with ContentType `application/vnd.openxmlformats-officedocument.wordprocessingml.comments+xml`
+
+## Typical insertion strategy
+- Identify the target paragraph or run range in `document.xml`.
+- Insert `commentRangeStart` before the first run you want covered.
+- Insert `commentRangeEnd` after the last run you want covered.
+- Append a run containing `commentReference`.
+- Create or append the comment body in `comments.xml`.
+
+## Recommended: use the helper script
+See `scripts/docx_ooxml_patch.py` (`--add-comment`). It:
+- auto-picks a non-colliding comment id by scanning the DOCX
+- **appends** to `word/comments.xml` if it already exists (does not overwrite existing comments)
+- reuses an existing comments relationship if present (avoids duplicate rels)
+
+## Structural verification checklist
+- `comments.xml` present in the ZIP
+- `document.xml.rels` has a comments relationship
+- `[Content_Types].xml` includes the Override
+- For each comment id, `document.xml` has start/end/reference anchors

package/resources/local/codex/plugins/cache/openai-primary-runtime/documents/26.505.10851/skills/documents/ooxml/hyperlinks_and_fields.md

@@ -0,0 +1,69 @@
+# OOXML: Hyperlinks, headers/footers, and fields (page numbers)
+
+This file covers the common "small but annoying" features that often require OOXML or low-level python-docx work.
+
+## Hyperlinks
+### Reality
+`python-docx` can create external hyperlink relationships but does not provide a high-level hyperlink API. The easiest path is to build the `<w:hyperlink>` element manually.
+
+### Pattern (external hyperlink)
+1) Create a relationship to the URL (Type = `RT.HYPERLINK`)
+2) Insert a `<w:hyperlink r:id="...">` containing a run with a `<w:t>`
+
+Minimal python-docx snippet:
+```python
+from docx.opc.constants import RELATIONSHIP_TYPE as RT
+from docx.oxml import OxmlElement
+from docx.oxml.ns import qn
+
+p = doc.paragraphs[0]
+url = "https://example.com"
+r_id = p.part.relate_to(url, RT.HYPERLINK, is_external=True)
+
+hyperlink = OxmlElement("w:hyperlink")
+hyperlink.set(qn("r:id"), r_id)
+
+r = OxmlElement("w:r")
+rPr = OxmlElement("w:rPr")
+# optional styling (blue + underline)
+color = OxmlElement("w:color"); color.set(qn("w:val"), "0000FF"); rPr.append(color)
+u = OxmlElement("w:u"); u.set(qn("w:val"), "single"); rPr.append(u)
+r.append(rPr)
+
+t = OxmlElement("w:t"); t.text = "link text"; r.append(t)
+hyperlink.append(r)
+p._p.append(hyperlink)
+```
+
+## Headers and footers
+### Right-aligned date header
+Most of the time python-docx is enough:
+```python
+from docx.enum.text import WD_ALIGN_PARAGRAPH
+section = doc.sections[0]
+hp = section.header.paragraphs[0]
+hp.alignment = WD_ALIGN_PARAGRAPH.RIGHT
+hp.text = "Date: 01/05/2026"
+```
+
+### Footer left/center/right zones
+A common reliable trick is a 1x3 table (remember: width required in headers/footers):
+```python
+from docx.shared import Inches
+from docx.enum.text import WD_ALIGN_PARAGRAPH
+footer = doc.sections[0].footer
+table = footer.add_table(rows=1, cols=3, width=Inches(6.5))
+# set paragraph alignment per cell
+```
+
+## Page number field
+### Reality
+A PAGE field is a Word field code. Some renderers may show placeholder values in PDF unless fields are updated.
+
+### Pattern
+Insert a field with `w:fldChar` begin/separate/end and an `w:instrText` of `PAGE`.
+
+See `scripts/docx_ooxml_patch.py` for helpers that add a centered page number field to the footer and add an external hyperlink.
+
+### Helper limitations (intentional)
+The `--hyperlink-first` helper is pragmatic: it replaces the first paragraph with a single linked run. It does not preserve per-run formatting. It does preserve leading/trailing spaces via `xml:space="preserve"` when needed.

package/resources/local/codex/plugins/cache/openai-primary-runtime/documents/26.505.10851/skills/documents/ooxml/rels_and_content_types.md

@@ -0,0 +1,37 @@
+# OOXML: Relationships and content types (the plumbing)
+
+These files are the most common reason a "patched" DOCX opens but features don't work.
+
+## Key files
+- `word/_rels/document.xml.rels` (relationships for the main document)
+- `[Content_Types].xml` (MIME types for parts)
+
+## Relationships: `word/_rels/document.xml.rels`
+- Namespace: `http://schemas.openxmlformats.org/package/2006/relationships`
+- Each `Relationship` has:
+  - `Id` (e.g., `rIdComments1`)
+  - `Type` (e.g., comments, hyperlinks, footer)
+  - `Target` (e.g., `comments.xml`)
+
+Example relationship for comments:
+```xml
+<Relationship Id="rIdComments1"
+  Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/comments"
+  Target="comments.xml"/>
+```
+
+## Content types: `[Content_Types].xml`
+- Namespace: `http://schemas.openxmlformats.org/package/2006/content-types`
+- For new parts (like `comments.xml`), add an `Override`:
+
+```xml
+<Override PartName="/word/comments.xml"
+  ContentType="application/vnd.openxmlformats-officedocument.wordprocessingml.comments+xml"/>
+```
+
+## Troubleshooting checklist
+If Word says the doc is corrupted or features don't appear:
+- Check that the part exists in the ZIP at the expected path
+- Check `document.xml.rels` has the correct `Type` and `Target`
+- Check `[Content_Types].xml` contains the `Override`
+- Check namespace prefixes are correct (Word is picky)

package/resources/local/codex/plugins/cache/openai-primary-runtime/documents/26.505.10851/skills/documents/ooxml/tracked_changes.md

@@ -0,0 +1,41 @@
+# OOXML: Tracked changes (true redlines)
+
+## When to use
+Use OOXML patching when the user needs *real* Word tracked changes, i.e. redlines that appear as insertions/deletions in Word.
+
+`python-docx` does **not** provide a first-class API for tracked changes.
+
+## Minimum wiring
+Tracked changes typically involve:
+- `word/settings.xml`: add `<w:trackRevisions/>` to enable tracking mode
+- `word/document.xml`: wrap inserted runs with `<w:ins ...>` and deletions with `<w:del ...>`
+
+## Key rules (to avoid broken docs)
+- IDs: `w:id` should be an integer string and **must not collide** with existing ids in the document
+- `w:author` and `w:date` are strongly recommended
+- Deletions must use `<w:delText>` (not `<w:t>`) inside `<w:del>`
+- Word can split text into many runs; operate at run granularity
+
+## Example pattern: replace a word via tracked delete + tracked insert
+Pseudo-structure:
+
+```xml
+<w:del w:id="202" w:author="ChatGPT" w:date="...">
+  <w:r><w:delText> old text </w:delText></w:r>
+</w:del>
+<w:ins w:id="203" w:author="ChatGPT" w:date="...">
+  <w:r><w:t> new text </w:t></w:r>
+</w:ins>
+```
+
+## Recommended: use the helper script
+See `scripts/docx_ooxml_patch.py` for a runnable patcher that:
+- enables `<w:trackRevisions/>`
+- converts an existing `<w:ins>` to `<w:del>` and inserts a new `<w:ins>`
+
+The CLI defaults to auto-generated `w:id` values (`--del-id auto --ins-id auto`) by scanning existing ids and choosing new ones.
+
+## Verification
+- Render to PDF/PNG for layout sanity (`tasks/verify_render.md`)
+- Confirm Word shows the change as tracked
+- Be aware: renders usually show redlines, but always verify the OOXML is correct too

package/resources/local/codex/plugins/cache/openai-primary-runtime/documents/26.505.10851/skills/documents/references/design_presets.md

@@ -0,0 +1,243 @@
+# Design Presets
+
+Use this reference for new DOCX creation and major rewrites. Existing-document edits should preserve the source document's style unless the user asks for a redesign.
+
+## Required workflow
+
+1. Pick exactly one preset or archetype alias before drafting.
+2. Resolve it into a concrete token map with exact values for every preset-controlled property: page geometry, margins, header/footer distance, body spacing, heading spacing, line spacing, list marker alignment, list text indent, hanging indent, table widths, table indents, cell margins, colors, and fills.
+3. Apply the tokens through Word styles, real numbering definitions, explicit table geometry, callout styles, headers, and footers.
+4. Treat any deviation as a named override and reuse that override consistently.
+5. Before rendering, audit the DOCX against the selected token map, including direct inspection of styles, numbering definitions, section properties, and table XML when needed.
+
+Do not combine presets in one document unless the user explicitly asks for a mixed style system. Do not rely on Word defaults, inherited built-in style values, or approximate visual matches. If a value appears in the selected preset, encode that exact value in the DOCX.
+
+## Exactness requirement
+
+Preset compliance means the generated DOCX carries the selected preset's actual numbers:
+
+- Paragraph styles must encode the preset's font, size, color, `before`, `after`, and line spacing values. For OOXML, this means values such as `w:before`, `w:after`, and `w:line` are present where the preset controls them.
+- Lists must use numbering definitions whose marker alignment, text indent, hanging indent, tab stop, paragraph spacing, and line spacing match the preset. Built-in styles such as `List Bullet` or `List Number` are acceptable only after their numbering definitions have been set or patched to the preset values.
+- Tables must use fixed DXA geometry. `tblW`, `tblGrid/gridCol`, and every `tcW` must agree with the preset or a named table-pattern override. `tblInd` must match the start cell margin token so the visible outer border aligns with surrounding paragraph text.
+- Table-adjacent citation text must use the selected preset's `table_citation_text` component token instead of inheriting body or caption defaults.
+- Page setup must encode the preset's page size, margins, usable width, and header/footer distances in section properties.
+- Named overrides are allowed only when the document needs a specific exception. Record the override and apply it consistently; do not let ad-hoc direct formatting drift across similar elements.
+
+## Shared base tokens
+
+All presets inherit these values unless they override them.
+
+| Token | Value |
+|---|---|
+| Page size | US Letter, 8.5 x 11 in, portrait |
+| Margins | 1.0 in top/right/bottom/left |
+| Header/footer distance | 0.492 in |
+| Usable width | 6.5 in / 9360 DXA |
+| Base body style | `Normal` |
+| Default base font | Calibri |
+| Default base size | 11 pt |
+| Heading 1 | 16 pt, `#2E74B5` |
+| Heading 2 | 13 pt, `#2E74B5` |
+| Heading 3 | 12 pt, `#1F4D78` |
+| Table width | 6.5 in / 9360 DXA |
+| Table indent | 120 DXA / 0.083 in, matching default start cell margin |
+| Table geometry | fixed DXA `tblW`, `tblInd`, `tblGrid`, and matching `tcW` |
+| Table default visual | thin single grid, white body cells, restrained optional header/callout fill |
+| Header/footer style | quiet running label/header rule and muted right-aligned page number for multi-page polished docs |
+
+## OOXML conversion cheatsheet
+
+| Design value | OOXML value |
+|---|---|
+| 1.0 in | 1440 DXA |
+| 6.5 in content/table width | 9360 DXA |
+| 0.083 in table indent / cell start margin | 120 DXA |
+| 0.5 in list text indent | 720 DXA |
+| 0.38 in list text indent | about 540 DXA |
+| 0.25 in marker alignment | 360 DXA |
+| 0.18 in marker alignment | about 260 DXA |
+| 0.19 in hanging indent | about 270 DXA |
+| 10 pt before | `w:before="200"` |
+| 8 pt after | `w:after="160"` |
+| 7 pt after | `w:after="140"` |
+| 6 pt after | `w:after="120"` |
+| 5 pt after | `w:after="100"` |
+| 4 pt before | `w:before="80"` |
+| 4 pt after | `w:after="80"` |
+| 3 pt after | `w:after="60"` |
+| 1.333 line spacing | `w:line="320" w:lineRule="auto"` |
+| 1.25 line spacing | `w:line="300" w:lineRule="auto"` |
+| 1.208 line spacing | `w:line="290" w:lineRule="auto"` |
+| 1.167 line spacing | `w:line="280" w:lineRule="auto"` |
+
+## Preset token schema
+
+Use this shape mentally or in builder code. Fill every value before writing content.
+
+```yaml
+document_style_preset:
+  preset_name: "<resolved preset or alias>"
+  page:
+    size: Letter
+    orientation: portrait
+    margins: {top: 1.0in, right: 1.0in, bottom: 1.0in, left: 1.0in}
+    header: 0.492in
+    footer: 0.492in
+    content_width: {in: 6.5, dxa: 9360}
+  typography:
+    base_font: "<font>"
+    base_size: 11pt
+    body: {alignment: left, before: 0pt, after: "<pt>", line_spacing: "<single|multiple>"}
+  headings:
+    h1: {size: 16pt, color: "#2E74B5", before: "<pt>", after: "<pt>"}
+    h2: {size: 13pt, color: "#2E74B5", before: "<pt>", after: "<pt>"}
+    h3: {size: 12pt, color: "#1F4D78", before: "<pt>", after: "<pt>"}
+  lists:
+    bullet_level_0: {marker: "•", marker_aligned_at: "<in>", text_indent_at: "<in>", hanging: "<in>", after: "<pt>", line_spacing: "<single|multiple>"}
+    decimal_level_0: {marker: "%1.", marker_aligned_at: "<in>", text_indent_at: "<in>", hanging: "<in>", after: "<pt>", line_spacing: "<single|multiple>"}
+  tables:
+    width_dxa: 9360
+    indent_dxa: 120
+    border_style: single_grid
+    header_fill: "<hex|none>"
+    cell_margins_dxa: {top: 80, bottom: 80, start: 120, end: 120}
+  table_citation_text:
+    use: "source/citation text immediately above or below a table"
+    paragraph: {before: 4pt, after: 4pt}
+  colors:
+    heading_blue: "#2E74B5"
+    heading_dark_blue: "#1F4D78"
+    ink_blue: "#0B2545"
+    table_fill_blue_gray: "#E8EEF5"
+    table_fill_light_gray: "#F2F4F7"
+    callout_fill: "#F4F6F9"
+    positive_dark_blue: "#1F3A5F"
+    caution_gold: "#7A5A00"
+    risk_red: "#9B1C1C"
+```
+
+## Base presets
+
+### `standard_business_brief`
+
+Use for formal memos, RFI responses, decision memos, board memos, and executive briefs.
+
+```yaml
+preset_name: standard_business_brief
+typography:
+  base_font: Calibri
+  body: {size: 11pt, alignment: left, before: 0pt, after: 6pt, line_spacing: 1.10}
+headings:
+  h1: {size: 16pt, color: "#2E74B5", before: 16pt, after: 8pt}
+  h2: {size: 13pt, color: "#2E74B5", before: 12pt, after: 6pt}
+  h3: {size: 12pt, color: "#1F4D78", before: 8pt, after: 4pt}
+lists:
+  bullet_level_0: {marker_aligned_at: 0.25in, text_indent_at: 0.5in, hanging: 0.25in, after: 8pt, line_spacing: 1.167}
+  decimal_level_0: {marker_aligned_at: 0.25in, text_indent_at: 0.5in, hanging: 0.25in, after: 8pt, line_spacing: 1.167}
+tables:
+  width_dxa: 9360
+  indent_dxa: 120
+  cell_margins_dxa: {top: 80, bottom: 80, start: 120, end: 120}
+  border_style: single_grid
+  header_fill: "#F2F4F7"
+table_citation_text:
+  use: "source/citation text immediately above or below a table"
+  paragraph: {before: 4pt, after: 4pt}
+```
+
+### `compact_reference_guide`
+
+Use for launch guides, negotiation briefs, checklists, and dense operator references.
+
+```yaml
+preset_name: compact_reference_guide
+typography:
+  base_font: Calibri
+  body: {size: 11pt, alignment: left, before: 0pt, after: 6pt, line_spacing: 1.25}
+headings:
+  h1: {size: 16pt, color: "#2E74B5", before: 18pt, after: 10pt}
+  h2: {size: 13pt, color: "#2E74B5", before: 14pt, after: 7pt}
+  h3: {size: 12pt, color: "#1F4D78", before: 10pt, after: 5pt}
+lists:
+  bullet_level_0: {marker_aligned_at: 0.187in, text_indent_at: 0.375in, hanging: 0.188in, after: 4pt, line_spacing: 1.25}
+  decimal_level_0: {marker_aligned_at: 0.187in, text_indent_at: 0.375in, hanging: 0.188in, after: 4pt, line_spacing: 1.25}
+tables:
+  width_dxa: 9360
+  indent_dxa: 120
+  cell_margins_dxa: {top: 80, bottom: 80, start: 120, end: 120}
+  border_style: single_grid
+  header_fill: "#E8EEF5"
+  compact_label_detail_widths: [1.181in, 5.319in]
+  standard_label_detail_widths: [1.875in, 4.625in]
+table_citation_text:
+  use: "source/citation text immediately above or below a table"
+  paragraph: {before: 4pt, after: 4pt}
+```
+
+### `narrative_proposal`
+
+Use for grant proposals, business proposals, and persuasive documents with longer prose.
+
+```yaml
+preset_name: narrative_proposal
+typography:
+  base_font: Calibri
+  body: {size: 11pt, alignment: justified, before: 0pt, after: 8pt, line_spacing: 1.333}
+headings:
+  h1: {size: 16pt, color: "#2E74B5", before: 18pt, after: 10pt}
+  h2: {size: 13pt, color: "#2E74B5", before: 12pt, after: 6pt}
+  h3: {size: 12pt, color: "#1F4D78", before: 8pt, after: 4pt}
+lists:
+  bullet_level_0: {marker_aligned_at: 0.181in, text_indent_at: 0.375in, hanging: 0.194in, after: 4pt, line_spacing: 1.208}
+  decimal_level_0: {marker_aligned_at: 0.181in, text_indent_at: 0.375in, hanging: 0.194in, after: 4pt, line_spacing: 1.208}
+tables:
+  width_dxa: 9360
+  indent_dxa: 120
+  cell_margins_dxa: {top: 80, bottom: 80, start: 120, end: 120}
+  border_style: single_grid
+  header_fill: "#F4F6F9"
+table_citation_text:
+  use: "source/citation text immediately above or below a table"
+  paragraph: {before: 4pt, after: 4pt}
+```
+
+## Archetype aliases
+
+Aliases inherit a base preset and override only the listed values.
+
+| Alias | Base preset | Overrides |
+|---|---|---|
+| `rfi_response` | `standard_business_brief` | Body after 6pt; H1 before 16pt/after 8pt; H2 before 12pt/after 6pt; list marker 0.25in, text 0.5in; use 3-4 column full-width compliance matrices. |
+| `decision_memo` | `standard_business_brief` | Base font Arial; body after 6pt; H1 before 12pt/after 6pt; H2 before 10pt/after 5pt; list marker 0.25in, text 0.5in. |
+| `launch_messaging_guide` | `compact_reference_guide` | Body after 6pt, line 1.25; H1 before 18pt/after 10pt; H2 before 14pt/after 7pt; H3 before 10pt/after 5pt; table use can be heavy. |
+| `contract_negotiation_brief` | `compact_reference_guide` | Body after 6pt; H1 before 14pt/after 8pt; H2 before 11pt/after 6pt; H3 before 8pt/after 4pt; prefer 1.181in/5.319in label-detail grids. |
+| `neighborhood_business_proposal` | `narrative_proposal` | Body justified, after 8pt, line 1.333; H1 before 18pt/after 10pt; H2 before 12pt/after 6pt; H3 before 8pt/after 4pt; decimal lists may lead action sequences. |
+| `grant_proposal` | `narrative_proposal` | Body left or justified by section, after 6pt, line 1.25 for compact prose; H1 before 16pt/after 8pt; H2 before 12pt/after 6pt; reserve tables for budget and evaluation. |
+
+## Table patterns
+
+Use full-width tables by default. Pick column widths by content and keep the total at 9360 DXA. Use `tblInd=120` DXA unless a named override intentionally changes table placement; this aligns the visible outer border with surrounding paragraph text instead of aligning only the first cell's text.
+
+| Pattern | Widths | Use |
+|---|---|---|
+| One-column callout | 6.5 in | Message blocks, grouped examples, callouts. |
+| Compact label-detail | 1.181 in, 5.319 in | Term/value, clause/position, compact reference rows. |
+| Standard label-detail | 1.875 in, 4.625 in | Brief metadata, description tables, playbooks. |
+| Two-up comparison | 3.25 in, 3.25 in | Option A/B, do/don't, before/after. |
+| Three-column matrix | 1.5 in, 2.5 in, 2.5 in | Decision criteria, stakeholder impact, roadmap. |
+| Four-column matrix | content-specific, sum 6.5 in | RFI compliance, budget, status, risk tables. |
+
+Always run the table geometry helper or an equivalent audit after table generation.
+
+## Preset audit
+
+Before final render review, verify:
+
+- Page size, margins, header/footer distance, and content width match the token map.
+- Body and heading styles carry the selected font, size, color, spacing, and line spacing.
+- Lists use real numbering definitions with the selected marker alignment, text indent, hanging indent, spacing, and line spacing.
+- Tables use 9360 DXA unless intentionally compact, `tblInd` equals the start cell margin token, and `tblW`, `tblGrid`, and each `tcW` agree.
+- Table-adjacent citation text above or below tables carries the selected preset's `table_citation_text` spacing.
+- Callout/header/table fills use only the preset colors or a named override.
+- Headers and footers are consistent across pages.
+- There are no fake headings, fake bullets, manual numbering, percentage-width tables, fixed row heights that clip, or unexplained direct formatting drift.