@ryuenn3123/agentic-senior-core 4.3.13 → 4.3.15

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

@@ -15,7 +15,7 @@ When a new project is created or initialized, the agent must automatically:
 ## Required Planning Mode
 
 If the user describes a project or feature, the agent must:
-1. Clarify the delivery goals, runtime assumptions, constraints, and must-have capabilities before choosing implementation shape.
+1. Before drafting docs from a thin or ambiguous brief, ask the smallest useful set of clarifying questions needed to make delivery goals, edge cases, constraints, must-have capabilities, and non-goals explicit. If the user wants a draft anyway, document assumptions and wait for approval before coding.
 2. If the user already named a stack or framework, treat it as an explicit constraint. If not, produce a short evidence-backed recommendation from the brief, repo evidence, and live official documentation before coding. Include at least one plausible alternative when the default-looking option is Next.js, Tailwind-only styling, shadcn/ui, or another familiar web stack.
 3. For existing projects, inspect real files first. Do not derive product name, description, runtime, architecture, or design direction from the folder name alone.
 4. Draft a high-level structure plan plus the docs/bootstrap artifacts that must exist before coding.

package/.agent-context/prompts/refactor.md

@@ -29,6 +29,7 @@ Refactor rules:
 - Prefer the shorter implementation only when it keeps the same guarantees.
 - Run a final simplification pass before completion.
 - Update tests and docs whenever behavior contracts, public APIs, data shape, or UI contracts change.
+- When fixing a bug: append one sentence to the nearest relevant doc (`docs/flow-overview.md` or `docs/architecture-decision-record.md`) naming the root cause and how to prevent recurrence.
 
 For every meaningful change, explain:
 - what risk or friction existed

package/AGENTS.md

@@ -17,21 +17,20 @@ Write instructions as imperative gates:
 - Move detailed policy into `.agent-context/`.
 - Add validation when a rule can drift.
 
-## Bootstrap Receipt
-For non-trivial work, run `agentic-senior-core context "<task_description>"` (or `npx @ryuenn3123/agentic-senior-core context "<task_description>"`) and emit a concise Bootstrap Receipt before implementation output or file edits:
+## MANDATORY FIRST STEP: Context Activation
+STOP. Before generating ANY plan, code, or design for a non-trivial task, you MUST run `agentic-senior-core context "<task_description>"` (or `npx @ryuenn3123/agentic-senior-core context "<task_description>"`) to resolve scopes. Do not guess or hallucinate context.
+
+Immediately emit a concise Bootstrap Receipt:
 - `loaded_files`: files actually read (exact paths from selectedRules/selectedPrompts only; zero hallucination)
 - `selected_rules`: files selected for this scope and why
 - `skipped_rules`: out-of-scope categories left unloaded
 - `unreachable_files`: required files that could not be read
 - `validation_plan`: expected checks before completion
 
-Keep it short. Do not load every rule just to fill it out.
-
-## Default Activation And Command Economy
-Before any non-trivial task, run `agentic-senior-core context "<task_description>"` and emit the Bootstrap Receipt. Skip only for trivial tasks: version bumps, typo fixes, single-line commits.
-Always prefix noisy shell commands: `ascx git status`, `ascx git diff`, `ascx npm test`, `ascx npm install`, `ascx npm run build`, `ascx tsc`, `ascx rg` searches. Use raw commands only for pipes, redirects, or commands not supported by ascx.
-Always read and apply `.agent-context/prompts/compact-natural-mode.md` for every final user-facing reply. Never repeat full command output; reference tee file paths when truncated.
+Skip this step ONLY for trivial tasks (version bumps, typo fixes).
 
+## Command Economy
+Use noisy command forms: `ascx git status`, `ascx git diff`, `ascx npm test`, `ascx npm install`, `ascx npm run build`, `ascx tsc`, `ascx rg`. Use raw commands only for pipes/redirects or unsupported commands. Apply `.agent-context/prompts/compact-natural-mode.md` for every final reply; never repeat full output; reference tee paths when truncated.
 ## Layer Index
 ### Layer 1: Rules (18 Files) [SCOPE-RESOLVED]
 Location: `.agent-context/rules/`.
@@ -40,7 +39,6 @@ Load only relevant rule files. Do not read the entire rule directory by default.
 
 Available rules: `architecture.md` (`ARCH-*`, v4), `security.md` (`SEC-*`, v4), `performance.md` (`PERF-*`, v4), `error-handling.md` (`ERR-*`, v4), `testing.md` (`TEST-*`, v4), `api-docs.md` (`API-*`, v4), `microservices.md` (`SVC-*`, v4), `event-driven.md` (`EVT-*`, v4), `database-design.md` (`DATA-*`, v4), `realtime.md` (`RT-*`, v4), `frontend-architecture.md` (`FE-*`, v4), `docker-runtime.md` (`DOCK-*`, v4), `observability.md` (`OBS-*`, v4), `resilience.md` (`RES-*`, v4), `migrations.md` (`MIG-*`, v4), `background-jobs.md` (`JOB-*`, v4), `config-and-flags.md` (`CFG-*`, v4), `api-versioning.md` (`VER-*`, v4).
 
-
 For Docker or Compose work, load `docker-runtime.md` and verify the latest official Docker docs before authoring container assets. Also perform live web research for Docker and framework/package setup claims. For framework or package setup work, use the latest stable compatible dependency set and official setup flow unless a documented compatibility constraint blocks it; prefer official framework scaffolders when they create the supported project shape. New dependencies are allowed when they improve efficiency, delivery time, correctness, accessibility, UX, or maintainability. Do not treat dependency avoidance or vague performance fear as a default reason to skip a modern maintained library.
 
 Backend/API routing:
@@ -171,4 +169,11 @@ Verify reachability of relevant files in Layer 1 to Layer 9 before generating im
 - Before PR: run review checklists.
 - Before deploy: check policy thresholds.
 - Before major refactor: read `architecture-map.md`.
-- Before UI implementation: confirm valid style context, design contract, and required docs.
+- Before UI implementation: confirm valid style context, design contract, and required docs.
+
+## Git Workflow
+Branch from main with `feat/`, `fix/`, `docs/`, or `chore/`; no direct commits to main. Use Conventional Commits: `feat:`, `fix:`, `docs:`, `refactor:`, `chore:`, `test:`.
+PRs use squash merge only, clean Markdown summaries, a Testing section, and `npm run validate` before opening. Bug fixes add one root-cause/prevention sentence to the nearest relevant doc.
+
+## Do Not Modify
+Never touch `.agentic-backup/`. Update `package-lock.json` only via `ascx npm install`. Preserve user entries in `.agent-context/state/active-memory.json`. Regenerate `benchmarks/results/` via npm scripts only.

package/package.json

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