From ed477aa72fd916c9f96417cf138f23f899e46bdc Mon Sep 17 00:00:00 2001 From: Jason Woltje Date: Fri, 31 Jul 2026 09:22:15 -0500 Subject: [PATCH] style(framework): apply prettier to WRITING-STYLE.md so CI format passes (#965) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The `format` step of .woodpecker/ci.yml:89 (`pnpm format:check`) failed on pipeline 2111 for this branch. Reproduced on a bench with the lockfile-pinned prettier@3.8.1 against the repo .prettierrc and .prettierignore, using CI's exact glob: WRITING-STYLE.md was the only failing file. The change is mechanical and semantically null: markdown table cell padding and `*emphasis*` -> `_emphasis_`. Verified by normalizing both revisions (whitespace removed, `_`/`*` folded, table rules collapsed) — the results are byte-identical. This does not address the prose findings published on #965 (P1-P4); those await a ruling. The `test` step also failed on 2111, on a base ~40 commits stale — attribution for that failure needs this rerun, and is not claimed here. Co-authored-by: mos-dt-0 --- .../mosaic/framework/guides/WRITING-STYLE.md | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/packages/mosaic/framework/guides/WRITING-STYLE.md b/packages/mosaic/framework/guides/WRITING-STYLE.md index 695e2a41..6fae5706 100644 --- a/packages/mosaic/framework/guides/WRITING-STYLE.md +++ b/packages/mosaic/framework/guides/WRITING-STYLE.md @@ -11,13 +11,13 @@ certification. ## Scope — which standard governs which output -| Output type | Standard | -|---|---| -| Technical documentation (READMEs, runbooks, PRDs, procedures, ADRs, guides, acceptance criteria, design docs) | **MOS-STE** (this guide) | -| Source code and code comments | **Google Style Guide** for the language (§4) | -| Inter-agent comms | MOS-STE by default (concise, structured) | -| User-facing comms | **Per-user style choice** — read `USER.md` "Communication Preferences" (§5) | -| End-user prose the user owns (marketing, letters, personal writing, voice-matched content) | The user's declared voice. MOS-STE does NOT apply. | +| Output type | Standard | +| ------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | +| Technical documentation (READMEs, runbooks, PRDs, procedures, ADRs, guides, acceptance criteria, design docs) | **MOS-STE** (this guide) | +| Source code and code comments | **Google Style Guide** for the language (§4) | +| Inter-agent comms | MOS-STE by default (concise, structured) | +| User-facing comms | **Per-user style choice** — read `USER.md` "Communication Preferences" (§5) | +| End-user prose the user owns (marketing, letters, personal writing, voice-matched content) | The user's declared voice. MOS-STE does NOT apply. | **The user-voice carve-out is absolute.** Do not apply MOS-STE to content that must carry a specific human voice (for example a cover letter, a personal @@ -43,7 +43,7 @@ concepts in one predicate, the check can test the wrong concept and still pass. **Worked failure.** A rename used a witness predicate with three clauses: ref A present, ref B absent, tip committed from this host. Every clause tested the git -*ref* (the channel). The claim under test was about a *field inside the payload*. +_ref_ (the channel). The claim under test was about a _field inside the payload_. The word "beacon" named two concepts in one sentence. Deleting ref B was the next scheduled step. That step flips the last clause green and certifies a state in which the payload still names the wrong host. The predicate was one planned action @@ -115,11 +115,11 @@ values. The builder renders the style as prose bullets, not the token name, so match on the leading bullet the generated `USER.md` actually contains: -| `USER.md` leading bullet | Style | User-facing output | -|---|---|---| -| "Direct and concise" | `direct` (default) | MOS-STE structure — short, active, defined terms, tables for overview. | -| "Warm and conversational" | `friendly` | Warmer register. Full sentences, explain reasoning, fewer tables. | -| "Professional and structured" | `formal` | Professional and structured. Thorough, with explicit recommendations. | +| `USER.md` leading bullet | Style | User-facing output | +| ----------------------------- | ------------------ | ---------------------------------------------------------------------- | +| "Direct and concise" | `direct` (default) | MOS-STE structure — short, active, defined terms, tables for overview. | +| "Warm and conversational" | `friendly` | Warmer register. Full sentences, explain reasoning, fewer tables. | +| "Professional and structured" | `formal` | Professional and structured. Thorough, with explicit recommendations. | This setting governs **user-facing comms only**. It does not change the documentation standard (§3), which is always MOS-STE regardless of the value.