@ryuenn3123/agentic-senior-core 2.0.17 → 2.0.19

package/.agent-context/prompts/review-code.md

@@ -14,6 +14,7 @@ Use these checklists:
 1. Read .agent-context/review-checklists/pr-checklist.md — apply every item.
 2. Read .agent-context/review-checklists/security-audit.md — apply every item.
 3. Apply documentation scope rules exactly: This applies to documentation, release notes, onboarding text, review summaries, and agent-facing explanations.
+4. Treat scope-style findings as advisory unless they hide factual errors, contract mismatches, or non-negotiable violations.
 
 For EVERY violation found:
 - State the exact file and line

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

@@ -92,6 +92,7 @@ VERDICT: PASS / FAIL (X/Y items passed)
 
 ### 10. Documentation
 - [ ] 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
 - [ ] API endpoints have OpenAPI/Swagger documentation
 - [ ] Complex business logic has comments explaining WHY
 - [ ] Public functions/methods have JSDoc/docstrings

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

@@ -45,6 +45,12 @@ API docs and README updates are included in this scope.
 4. Rewrite and reorder content when flow is weak.
 5. Keep explanations short by default; expand only when complexity requires it.
 
+### Scope Severity and Merge Behavior
+1. Scope style guidance controls readability and consistency.
+2. Style baseline findings are advisory by default and must not block endpoint-change commits that already include accurate docs/spec updates.
+3. Hard blockers remain contract failures: missing same-commit docs sync, incorrect schema, missing required responses, or factual inaccuracies.
+4. If style polish is still needed, open a follow-up task instead of delaying the contract update.
+
 ### Non-Negotiables
 1. No emoji in formal artifacts.
 2. Avoid AI cliches and buzzwords: delve, leverage, robust, utilize, seamless.
@@ -198,6 +204,9 @@ This schema MUST be documented in OpenAPI as a reusable component (`#/components
 ```
 Endpoint changed + docs NOT updated = PR REJECTED.
 
+This sync rule has higher priority than style polish timing.
+Do not delay same-commit documentation sync only to iterate writing tone.
+
 The spec is a contract. If the contract is wrong, consumers will break.
 "I'll update the docs later" means "the docs will never be updated."
 ```