@ryuenn3123/agentic-senior-core 3.0.33 → 3.0.34

package/.agent-context/prompts/init-project.md

@@ -20,6 +20,15 @@ If the user describes a project or feature, the agent must:
 4. Draft a high-level structure plan plus the docs/bootstrap artifacts that must exist before coding.
 5. Wait for user approval before scaffolding the project.
 
+## Documentation-First Requests
+
+If the user asks to create, complete, fix, or review project docs, documentation, dokumen, `docs/*`, architecture docs, flow docs, API docs, or "lengkapkan docs", treat the request as documentation-first.
+
+The agent must:
+1. Materialize or refine required project docs before implementation: `docs/project-brief.md`, `docs/architecture-decision-record.md`, `docs/flow-overview.md`, `docs/api-contract.md` when APIs, firmware endpoints, CLI commands, or web application flows exist, `docs/database-schema.md` when persistent data exists, and `docs/DESIGN.md` plus `docs/design-intent.json` for UI scope.
+2. Write formal project docs in English by default unless the user explicitly asks for another documentation language.
+3. Stop after docs when the user only asked for docs. Do not write application, firmware, or UI code until the user explicitly asks for implementation or approves the implementation plan.
+
 ## Direct Constraint Mode
 
 If the user specifies a framework, runtime, or architecture constraint, the agent must:

package/.agent-context/review-checklists/pr-checklist.md

@@ -60,6 +60,8 @@ Run this before declaring a task done. Apply only the sections relevant to the c
 - [ ] Scope applied: This applies to documentation, release notes, onboarding text, review summaries, and agent-facing explanations
 - [ ] Style scope review is advisory and does not block merge when API docs are synced in the same commit and contract details are correct
 - [ ] Required docs exist before implementation: project brief, architecture decision, flow overview, API/public contract when relevant, data model when relevant, and UI design contract when relevant.
+- [ ] For docs-only or docs-first requests, implementation code was not changed unless the user explicitly asked for it or approved an implementation plan.
+- [ ] Formal project docs use English by default unless the user requested another language or existing docs established one.
 - [ ] Docs cover feature plan, architecture rationale, public contracts, data model, UI/design, security assumptions, testing strategy, delivery flow, and next validation actions where relevant.
 - [ ] API, event, CLI, library, data, and UI contract changes update docs in the same scope.
 - [ ] Public surface changes fail review if documentation updates are missing or stale in the same scope

package/.agent-context/rules/api-docs.md

@@ -24,6 +24,10 @@ If a change affects an API, CLI command, exported library behavior, schema, even
 This applies to documentation, release notes, onboarding text, review summaries, and agent-facing explanations.
 API docs and README updates are included in this scope.
 
+### Language Default
+
+Write formal project docs in English by default, even when the user prompt is in another language. Use another documentation language only when the user explicitly asks for it or when existing project docs already establish that language.
+
 ### Style Baseline
 
 1. Write for native English speakers.

package/.agent-context/state/memory-continuity-benchmark.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-04-26T22:56:14.192Z",
+  "generatedAt": "2026-04-26T23:40:08.786Z",
   "reportName": "memory-continuity-benchmark",
   "schemaVersion": "1.0.0",
   "passed": true,

package/.cursorrules

@@ -1,7 +1,7 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v3.0.33
-Timestamp: 2026-04-24T06:02:48.303Z
+Generated by Agentic-Senior-Core CLI v3.0.34
+Timestamp: 2026-04-26T23:31:29.580Z
 Selected policy file: .agent-context/policies/llm-judge-threshold.json
 
 ## GOVERNANCE PRECEDENCE
@@ -54,15 +54,20 @@ For an existing project, inspect repo markers and current files directly before
 Do not silently choose a stack from offline defaults.
 ## LAYER 2 POLICY: LAZY RULE LOADING
 Primary runtime constraint: unresolved until agent recommendation is approved
-Additional runtime guidance loads only when explicitly selected by the user or required by touched code.
-Load runtime-specific guidance only when task scope touches that runtime.
-Avoid eager loading unrelated runtime guidance to prevent instruction conflicts.
+No stack-specific governance adapter is loaded by default.
+Load global domain rules only when task scope touches that domain.
+Avoid eager loading unrelated runtime or domain guidance to prevent instruction conflicts.
 ## LAYER 5: EXECUTION PROMPTS AND UI TRIGGERS
 Load these prompt contracts only when their trigger matches the user request:
+0. Documentation-first mode -> docs, documentation, dokumen, docs/*, architecture docs, flow docs, API docs, lengkapkan docs
 1. .agent-context/prompts/init-project.md -> create, build, new project, scaffold
 2. .agent-context/prompts/refactor.md -> refactor, improve, clean up, fix
 3. .agent-context/prompts/review-code.md -> review, audit, check, analyze
 4. .agent-context/prompts/bootstrap-design.md -> ui, ux, layout, screen, tailwind, frontend, redesign
+Documentation-first policy:
+- Create or refine required project docs before implementation: docs/project-brief.md, docs/architecture-decision-record.md, docs/flow-overview.md, docs/api-contract.md when APIs, firmware endpoints, CLI commands, or web application flows exist, docs/database-schema.md when persistent data exists, and docs/DESIGN.md plus docs/design-intent.json for UI scope.
+- Write formal project docs in English by default unless the user explicitly asks for another documentation language.
+- For docs-only/docs-first requests, do not write application, firmware, or UI code until the user asks or approves an implementation plan.
 UI trigger policy:
 - Load .agent-context/prompts/bootstrap-design.md and .agent-context/rules/frontend-architecture.md first.
 - Keep UI-only requests context-isolated and do not eagerly load backend-only rules such as database-design.md, docker-runtime.md, microservices.md, git-workflow.md, or general implementation-theory rules unless the task explicitly crosses those boundaries.

package/.gemini/instructions.md

@@ -2,7 +2,7 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: a49781782fac817a8a979e7937563b67826fd088af160a12cf84bdab4d038624
+Canonical Snapshot SHA256: 06e3f81d1df0e86bad6c3fe2a4623da640a1ea88b3124aecf1c10214cdc178e6
 
 Canonical policy source: [.instructions.md](../.instructions.md).
 
@@ -11,6 +11,7 @@ If your host stops at this file, follow this minimum floor:
 - For UI or redesign requests, load [.agent-context/prompts/bootstrap-design.md](../.agent-context/prompts/bootstrap-design.md) and [.agent-context/rules/frontend-architecture.md](../.agent-context/rules/frontend-architecture.md) before coding.
 - For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
 - If UI scope and `docs/DESIGN.md` or `docs/design-intent.json` is missing, materialize them before UI implementation.
+- For documentation-first requests, create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
 - For backend/API/data/auth/event requests, load relevant global rules from [.agent-context/rules/](../.agent-context/rules) and do not create stack-specific governance adapters.
 - Memory continuity is host-dependent project memory and does not replace bootstrap loading.
 

package/.github/copilot-instructions.md

@@ -2,7 +2,7 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: a49781782fac817a8a979e7937563b67826fd088af160a12cf84bdab4d038624
+Canonical Snapshot SHA256: 06e3f81d1df0e86bad6c3fe2a4623da640a1ea88b3124aecf1c10214cdc178e6
 
 The canonical policy source for this repository is [.instructions.md](../.instructions.md).
 
@@ -11,6 +11,7 @@ If your host stops at this file, follow this minimum floor:
 - For UI or redesign requests, load [.agent-context/prompts/bootstrap-design.md](../.agent-context/prompts/bootstrap-design.md) and [.agent-context/rules/frontend-architecture.md](../.agent-context/rules/frontend-architecture.md) before coding.
 - For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
 - If UI scope and `docs/DESIGN.md` or `docs/design-intent.json` is missing, materialize them before UI implementation.
+- For documentation-first requests, create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
 - For backend/API/data/auth/event requests, load relevant global rules from [.agent-context/rules/](../.agent-context/rules) and do not create stack-specific governance adapters.
 - Memory continuity is host-dependent project memory and does not replace bootstrap loading.
 

package/.instructions.md

@@ -161,7 +161,18 @@ Use available MCP tools when you need validation, linting, or test execution.
 
 ## Mandatory Triggers
 
-### 1. New Project Planning
+### 1. Documentation-First Mode
+
+**Trigger**: User asks to create, complete, fix, or review project docs, documentation, dokumen, `docs/*`, architecture docs, flow docs, API docs, or "lengkapkan docs".
+
+**Workflow**:
+
+1. Load `architecture.md` and `api-docs.md`, then load only additional rules needed by the documented scope.
+2. Create or refine the required project docs before implementation: `docs/project-brief.md`, `docs/architecture-decision-record.md`, `docs/flow-overview.md`, `docs/api-contract.md` when APIs, firmware endpoints, CLI commands, or web application flows exist, `docs/database-schema.md` when persistent data exists, and `docs/DESIGN.md` plus `docs/design-intent.json` for UI scope.
+3. Write formal project docs in English by default unless the user explicitly asks for another documentation language.
+4. Stop after documentation when the user only asked for docs. Do not write application, firmware, or UI code until the user explicitly asks for implementation or approves the implementation plan.
+
+### 2. New Project Planning
 
 **Trigger**: User says "create", "build", "new project", or "scaffold"
 
@@ -173,7 +184,7 @@ Use available MCP tools when you need validation, linting, or test execution.
 4. Produce scope, required docs, implementation boundaries, and a runtime/architecture recommendation when those decisions are unresolved.
 5. **WAIT for user approval** before generating code.
 
-### 2. Refactor Mode (EXISTING CODE)
+### 3. Refactor Mode (EXISTING CODE)
 
 **Trigger**: User says "refactor", "improve", "fix", or "clean up"
 
@@ -185,7 +196,7 @@ Use available MCP tools when you need validation, linting, or test execution.
 4. Propose plan before executing changes.
 5. **WAIT for approval**.
 
-### 3. Code Review Mode
+### 4. Code Review Mode
 
 **Trigger**: User says "review", "audit", "check", or "analyze"
 
@@ -196,7 +207,7 @@ Use available MCP tools when you need validation, linting, or test execution.
 3. Execute review against the active rules and contracts.
 4. Generate a structured report.
 
-### 4. UI Design Mode
+### 5. UI Design Mode
 
 **Trigger**: User says "ui", "ux", "layout", "screen", "tailwind", "frontend", or "redesign"
 

package/.windsurfrules

@@ -1,7 +1,7 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v3.0.33
-Timestamp: 2026-04-24T06:02:48.303Z
+Generated by Agentic-Senior-Core CLI v3.0.34
+Timestamp: 2026-04-26T23:31:29.580Z
 Selected policy file: .agent-context/policies/llm-judge-threshold.json
 
 ## GOVERNANCE PRECEDENCE
@@ -54,15 +54,20 @@ For an existing project, inspect repo markers and current files directly before
 Do not silently choose a stack from offline defaults.
 ## LAYER 2 POLICY: LAZY RULE LOADING
 Primary runtime constraint: unresolved until agent recommendation is approved
-Additional runtime guidance loads only when explicitly selected by the user or required by touched code.
-Load runtime-specific guidance only when task scope touches that runtime.
-Avoid eager loading unrelated runtime guidance to prevent instruction conflicts.
+No stack-specific governance adapter is loaded by default.
+Load global domain rules only when task scope touches that domain.
+Avoid eager loading unrelated runtime or domain guidance to prevent instruction conflicts.
 ## LAYER 5: EXECUTION PROMPTS AND UI TRIGGERS
 Load these prompt contracts only when their trigger matches the user request:
+0. Documentation-first mode -> docs, documentation, dokumen, docs/*, architecture docs, flow docs, API docs, lengkapkan docs
 1. .agent-context/prompts/init-project.md -> create, build, new project, scaffold
 2. .agent-context/prompts/refactor.md -> refactor, improve, clean up, fix
 3. .agent-context/prompts/review-code.md -> review, audit, check, analyze
 4. .agent-context/prompts/bootstrap-design.md -> ui, ux, layout, screen, tailwind, frontend, redesign
+Documentation-first policy:
+- Create or refine required project docs before implementation: docs/project-brief.md, docs/architecture-decision-record.md, docs/flow-overview.md, docs/api-contract.md when APIs, firmware endpoints, CLI commands, or web application flows exist, docs/database-schema.md when persistent data exists, and docs/DESIGN.md plus docs/design-intent.json for UI scope.
+- Write formal project docs in English by default unless the user explicitly asks for another documentation language.
+- For docs-only/docs-first requests, do not write application, firmware, or UI code until the user asks or approves an implementation plan.
 UI trigger policy:
 - Load .agent-context/prompts/bootstrap-design.md and .agent-context/rules/frontend-architecture.md first.
 - Keep UI-only requests context-isolated and do not eagerly load backend-only rules such as database-design.md, docker-runtime.md, microservices.md, git-workflow.md, or general implementation-theory rules unless the task explicitly crosses those boundaries.

package/AGENTS.md

@@ -2,7 +2,7 @@
 
 Adapter Mode: thin
 Adapter Source: .instructions.md
-Canonical Snapshot SHA256: a49781782fac817a8a979e7937563b67826fd088af160a12cf84bdab4d038624
+Canonical Snapshot SHA256: 06e3f81d1df0e86bad6c3fe2a4623da640a1ea88b3124aecf1c10214cdc178e6
 
 This file is an adapter entrypoint for agent discovery.
 The canonical policy source is [.instructions.md](.instructions.md).
@@ -16,6 +16,7 @@ If your host stops at this file instead of following the full chain, obey the Cr
 - For UI, UX, layout, screen, tailwind, frontend, or redesign requests: load [.agent-context/prompts/bootstrap-design.md](.agent-context/prompts/bootstrap-design.md) and [.agent-context/rules/frontend-architecture.md](.agent-context/rules/frontend-architecture.md) before editing code.
 - For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
 - For UI scope: if `docs/DESIGN.md` or `docs/design-intent.json` is missing, materialize or refine them before implementing UI changes.
+- For documentation-first requests: create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
 - For backend, API, data, auth, error, event, queue, worker, or distributed-system requests: load the relevant global rules from [.agent-context/rules/](.agent-context/rules); do not create stack-specific governance adapters.
 - For refactor, improve, clean up, or fix requests: inspect the active rules and propose a plan before editing.
 - For new project or module requests: clarify constraints, runtime decisions, and required docs before generating code.

package/lib/cli/compiler.mjs

@@ -348,10 +348,15 @@ export async function buildCompiledRulesContent({
     [
       '## LAYER 5: EXECUTION PROMPTS AND UI TRIGGERS',
       'Load these prompt contracts only when their trigger matches the user request:',
+      '0. Documentation-first mode -> docs, documentation, dokumen, docs/*, architecture docs, flow docs, API docs, lengkapkan docs',
       '1. .agent-context/prompts/init-project.md -> create, build, new project, scaffold',
       '2. .agent-context/prompts/refactor.md -> refactor, improve, clean up, fix',
       '3. .agent-context/prompts/review-code.md -> review, audit, check, analyze',
       '4. .agent-context/prompts/bootstrap-design.md -> ui, ux, layout, screen, tailwind, frontend, redesign',
+      'Documentation-first policy:',
+      '- Create or refine required project docs before implementation: docs/project-brief.md, docs/architecture-decision-record.md, docs/flow-overview.md, docs/api-contract.md when APIs, firmware endpoints, CLI commands, or web application flows exist, docs/database-schema.md when persistent data exists, and docs/DESIGN.md plus docs/design-intent.json for UI scope.',
+      '- Write formal project docs in English by default unless the user explicitly asks for another documentation language.',
+      '- For docs-only/docs-first requests, do not write application, firmware, or UI code until the user asks or approves an implementation plan.',
       'UI trigger policy:',
       '- Load .agent-context/prompts/bootstrap-design.md and .agent-context/rules/frontend-architecture.md first.',
       '- Keep UI-only requests context-isolated and do not eagerly load backend-only rules such as database-design.md, docker-runtime.md, microservices.md, git-workflow.md, or general implementation-theory rules unless the task explicitly crosses those boundaries.',
@@ -536,6 +541,7 @@ export async function buildCompiledRulesContent({
         '- docs/flow-overview.md must also exist before coding continues.',
         '- Add docs/database-schema.md when persistent data is involved.',
         '- Add docs/api-contract.md when API or web application flows are involved.',
+        '- For docs-only/docs-first requests, stop after docs unless the user asks for implementation or approves an implementation plan.',
         '- If docs/project-brief.md is missing, execute bootstrap-project-context prompt immediately.',
         hasBootstrapDesignPrompt
           ? '- For UI scope: if docs/DESIGN.md or docs/design-intent.json is missing, execute bootstrap-design prompt before implementing UI surfaces.'

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ryuenn3123/agentic-senior-core",
-  "version": "3.0.33",
+  "version": "3.0.34",
   "type": "module",
   "description": "Force your AI Agent to code like a Staff Engineer, not a Junior.",
   "bin": {

package/scripts/sync-thin-adapters.mjs

@@ -45,6 +45,7 @@ If your host stops at this file instead of following the full chain, obey the Cr
 - For UI, UX, layout, screen, tailwind, frontend, or redesign requests: load [.agent-context/prompts/bootstrap-design.md](.agent-context/prompts/bootstrap-design.md) and [.agent-context/rules/frontend-architecture.md](.agent-context/rules/frontend-architecture.md) before editing code.
 - For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
 - For UI scope: if \`docs/DESIGN.md\` or \`docs/design-intent.json\` is missing, materialize or refine them before implementing UI changes.
+- For documentation-first requests: create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
 - For backend, API, data, auth, error, event, queue, worker, or distributed-system requests: load the relevant global rules from [.agent-context/rules/](.agent-context/rules); do not create stack-specific governance adapters.
 - For refactor, improve, clean up, or fix requests: inspect the active rules and propose a plan before editing.
 - For new project or module requests: clarify constraints, runtime decisions, and required docs before generating code.
@@ -89,6 +90,7 @@ If your host stops at this file, follow this minimum floor:
 - For UI or redesign requests, load [.agent-context/prompts/bootstrap-design.md](../.agent-context/prompts/bootstrap-design.md) and [.agent-context/rules/frontend-architecture.md](../.agent-context/rules/frontend-architecture.md) before coding.
 - For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
 - If UI scope and \`docs/DESIGN.md\` or \`docs/design-intent.json\` is missing, materialize them before UI implementation.
+- For documentation-first requests, create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
 - For backend/API/data/auth/event requests, load relevant global rules from [.agent-context/rules/](../.agent-context/rules) and do not create stack-specific governance adapters.
 - Memory continuity is host-dependent project memory and does not replace bootstrap loading.
 
@@ -126,6 +128,7 @@ If your host stops at this file, follow this minimum floor:
 - For UI or redesign requests, load [.agent-context/prompts/bootstrap-design.md](../.agent-context/prompts/bootstrap-design.md) and [.agent-context/rules/frontend-architecture.md](../.agent-context/rules/frontend-architecture.md) before coding.
 - For UI scope, include a one-line Motion/Palette Decision in the Bootstrap Receipt; product categories are heuristics, not style presets.
 - If UI scope and \`docs/DESIGN.md\` or \`docs/design-intent.json\` is missing, materialize them before UI implementation.
+- For documentation-first requests, create or refine required project docs in English by default and do not write application, firmware, or UI code until the user asks or approves.
 - For backend/API/data/auth/event requests, load relevant global rules from [.agent-context/rules/](../.agent-context/rules) and do not create stack-specific governance adapters.
 - Memory continuity is host-dependent project memory and does not replace bootstrap loading.
 

package/scripts/validate/config.mjs

@@ -24,6 +24,7 @@ export const REQUIRED_HUMAN_WRITING_SNIPPETS = [
       '## Human Writing Standard (Mandatory)',
       'This applies to documentation, release notes, onboarding text, review summaries, and agent-facing explanations.',
       'Style baseline findings are advisory by default and must not block endpoint-change commits that already include accurate docs/spec updates.',
+      'Write formal project docs in English by default',
       'No emoji in formal artifacts.',
     ],
   },
@@ -32,6 +33,7 @@ export const REQUIRED_HUMAN_WRITING_SNIPPETS = [
     snippets: [
       'Scope applied: This applies to documentation, release notes, onboarding text, review summaries, and agent-facing explanations',
       'Style scope review is advisory and does not block merge when API docs are synced in the same commit and contract details are correct',
+      'Formal project docs use English by default',
       'No emoji in formal documentation or review summaries',
       'Documentation uses plain English and avoids AI cliches',
     ],
@@ -179,6 +181,14 @@ export const REQUIRED_STACK_DECISION_BOUNDARY_SNIPPETS = [
   },
 ];
 export const REQUIRED_UNIVERSAL_SOP_SNIPPETS = [
+  {
+    path: '.instructions.md',
+    snippets: [
+      '### 1. Documentation-First Mode',
+      'Stop after documentation when the user only asked for docs.',
+      'Do not write application, firmware, or UI code',
+    ],
+  },
   {
     path: '.agent-context/rules/architecture.md',
     snippets: [
@@ -187,6 +197,14 @@ export const REQUIRED_UNIVERSAL_SOP_SNIPPETS = [
       'If required project context docs are missing, stop implementation and bootstrap docs before writing application code.',
     ],
   },
+  {
+    path: '.agent-context/prompts/init-project.md',
+    snippets: [
+      '## Documentation-First Requests',
+      'Stop after docs when the user only asked for docs.',
+      'Write formal project docs in English by default',
+    ],
+  },
   {
     path: '.agent-context/review-checklists/pr-checklist.md',
     snippets: [
@@ -212,6 +230,8 @@ export const REQUIRED_UNIVERSAL_SOP_SNIPPETS = [
     snippets: [
       'Universal SOP hard block policy:',
       'Hard block: do not write application code until docs/project-brief.md and docs/architecture-decision-record.md exist.',
+      'Documentation-first policy:',
+      'For docs-only/docs-first requests, do not write application, firmware, or UI code until the user asks or approves an implementation plan.',
       'For UI scope: if docs/DESIGN.md or docs/design-intent.json is missing, execute bootstrap-design prompt before implementing UI surfaces.',
     ],
   },
@@ -265,6 +285,9 @@ export const REQUIRED_UI_DESIGN_AUTOMATION_SNIPPETS = [
       'docs/DESIGN.md',
       'docs/design-intent.json',
       'does not replace bootstrap loading',
+      'documentation-first requests',
+      'English by default',
+      'do not write application, firmware, or UI code',
       'Motion/Palette Decision',
       'product categories are heuristics',
       'perform live web research',