chore: 문서를 작성할 때 한국어의 표현 작성 스킬 추가 및 1인칭 관점의 글 작성 검증 테스트 추가

examples/output/retry-policy-demo/inputs/brief.normalized.json

@@ -42,10 +42,13 @@
   "constraints": {
     "target_words": 1200,
     "tone": "운영 경험이 있는 엔지니어에게 설명하는 직접적이고 검증 가능한 문체",
-    "version_context": "HTTP 의미론은 RFC 9110, 예시는 2026-07-23 기준",
+    "version_context": "HTTP 메서드 의미론은 RFC 9110을 따른다.",
     "max_heading_depth": 3,
     "require_citations": true,
-    "allow_external_knowledge": false
+    "allow_external_knowledge": false,
+    "citation_style": "hidden",
+    "date_policy": "only_when_material",
+    "style_profile": "woowahan_tech_blog_ko"
   },
   "forbidden_claims": [
     "재시도는 항상 안전하다"

examples/output/retry-policy-demo/inputs/pipeline.normalized.json

@@ -19,6 +19,13 @@
       "timeout_seconds": 300,
       "options": {}
     },
+    {
+      "role": "decision",
+      "provider": "mock",
+      "model": "",
+      "timeout_seconds": 300,
+      "options": {}
+    },
     {
       "role": "reader",
       "provider": "mock",
@@ -26,6 +33,13 @@
       "timeout_seconds": 300,
       "options": {}
     },
+    {
+      "role": "editor",
+      "provider": "mock",
+      "model": "",
+      "timeout_seconds": 300,
+      "options": {}
+    },
     {
       "role": "evidence",
       "provider": "mock",

examples/output/retry-policy-demo/inputs/sources.normalized.json

@@ -11,7 +11,16 @@
         "Exponential backoff limits retry frequency, and jitter spreads retry timing across clients.",
         "Retry behavior should be bounded rather than continuing indefinitely."
       ],
-      "notes": "Use for retry-load, backoff, jitter, and bounded-retry claims."
+      "notes": "Use for retry-load, backoff, jitter, and bounded-retry claims.",
+      "source_type": "external",
+      "status": "",
+      "path": "",
+      "heading": "",
+      "line_start": null,
+      "line_end": null,
+      "claim_ids": [],
+      "decision_ids": [],
+      "priority": 0.0
     },
     {
       "id": "S2",
@@ -23,7 +32,16 @@
         "A request method is idempotent when multiple identical requests have the same intended effect as one request.",
         "A client can automatically retry an idempotent request after a communication failure before reading the response, subject to the specification's conditions."
       ],
-      "notes": "Use for the definition and retry implications of HTTP method idempotency."
+      "notes": "Use for the definition and retry implications of HTTP method idempotency.",
+      "source_type": "external",
+      "status": "",
+      "path": "",
+      "heading": "",
+      "line_start": null,
+      "line_end": null,
+      "claim_ids": [],
+      "decision_ids": [],
+      "priority": 0.0
     },
     {
       "id": "S3",
@@ -35,7 +53,16 @@
         "Retry behavior should consider whether the operation is idempotent.",
         "Exponential backoff increases the delay between retry attempts and should use bounded limits."
       ],
-      "notes": "Use as a second implementation-oriented source for bounded backoff and idempotency checks."
+      "notes": "Use as a second implementation-oriented source for bounded backoff and idempotency checks.",
+      "source_type": "external",
+      "status": "",
+      "path": "",
+      "heading": "",
+      "line_start": null,
+      "line_end": null,
+      "claim_ids": [],
+      "decision_ids": [],
+      "priority": 0.0
     }
   ]
 }