@ryuenn3123/agentic-senior-core 2.0.5 → 2.0.8

package/.agent-context/blueprints/mobile-app.md

@@ -1,21 +1,91 @@
-# Mobile App Blueprint
-
-This blueprint defines the starter shape for a mobile product that needs a clean separation between UI, device integration, and backend contracts.
-
-## Structure
-
-- Transport: device events, navigation entry points, push notifications, and platform channels.
-- Service: orchestration, screen-level state, validation, and user-facing workflows.
-- Repository: remote API clients, local storage adapters, and persistence abstractions.
-
-## Starter Rules
-
-- Keep screens focused on rendering and user interaction only.
-- Move API access, caching, and serialization into adapter layers.
-- Use consistent error handling for offline, permission, and platform failures.
-- Add release checks for signing, packaging, and crash telemetry before shipping.
-
-## Recommended Stack Pairings
-
-- React Native for teams that want JavaScript or TypeScript alignment.
-- Flutter for teams that want a strongly structured UI toolkit.
+# Mobile App Blueprint
+
+This blueprint defines a production starter for mobile products that need strict separation between UI flow, device integration, offline behavior, and backend contracts.
+
+## Reference Architecture
+
+Use a three-layer mobile module boundary:
+
+- Transport layer: navigation routes, deep links, push notification handlers, platform lifecycle hooks.
+- Service layer: screen orchestration, input validation, business workflows, permission policy decisions.
+- Repository layer: API clients, local persistence, cache synchronization, device adapter wrappers.
+
+## Suggested Structure
+
+```text
+mobile/
+	app/
+		navigation/
+		screens/
+		feature-flags/
+	features/
+		checkout/
+			ui/
+			service/
+			repository/
+			contracts/
+			tests/
+			index.ts
+		account/
+			ui/
+			service/
+			repository/
+			contracts/
+			tests/
+			index.ts
+	shared/
+		design-tokens/
+		telemetry/
+		error-boundaries/
+		accessibility/
+```
+
+## State and Data Rules
+
+- Keep transient UI state local to the screen component.
+- Keep feature workflow state in service-level orchestrators.
+- Keep remote and local synchronization logic in repository adapters.
+- Enforce idempotent retry semantics for background sync and push-triggered refresh.
+
+## Device and Platform Boundaries
+
+- Wrap native modules behind explicit interfaces.
+- Keep iOS/Android-specific behavior in adapter files, not in feature UI components.
+- Centralize permission checks for camera, location, notifications, and storage.
+- Define fallback behavior for denied permissions before QA sign-off.
+
+## Offline and Failure Handling
+
+- Define offline-first behavior per feature (read-only, queued writes, or blocked operations).
+- Persist pending mutations with retry metadata.
+- Show explicit user-facing recovery actions for network and permission failures.
+- Log mobile crash context with feature name, operation, and user impact summary.
+
+## Testing Baseline
+
+- Unit tests: service decisions, validation, and adapter boundary behavior.
+- Integration tests: repository sync logic with mocked device/network behavior.
+- End-to-end tests: critical journeys (login, primary conversion flow, error recovery path).
+- Accessibility checks: screen reader labels, focus order, and reduced-motion behavior.
+
+## Release Governance
+
+Before shipping each mobile release candidate:
+
+- Verify signing and packaging pipeline integrity.
+- Verify crash-free session and startup stability thresholds.
+- Verify telemetry/analytics payload schema compatibility.
+- Verify rollback strategy for binary release and remote config toggles.
+
+## Recommended Stack Pairings
+
+- React Native for teams that want JavaScript or TypeScript alignment and shared web hiring pool.
+- Flutter for teams that want consistent rendering across platforms and widget-driven architecture.
+
+## Blueprint Checklist
+
+- [ ] Feature boundaries are modular and explicit.
+- [ ] Device adapters are isolated from UI rendering code.
+- [ ] Offline and permission failure behavior is documented.
+- [ ] Critical mobile journeys are covered by automated tests.
+- [ ] Release package and telemetry gates are enforced before ship.

package/.agent-context/profiles/platform.md

@@ -1,13 +1,13 @@
-# Team Profile Pack: Platform
-
-slug: platform
-displayName: Platform Team
-description: Reliability-oriented defaults for shared platform modules across teams.
-defaultProfile: balanced
-defaultStack: go.md
-defaultBlueprint: go-service.md
-ciGuardrails: true
-lockCi: false
-blockingSeverities: critical, high
-owner: platform-foundation
-lastUpdated: 2026-03-19
+# Team Profile Pack: Platform
+
+slug: platform
+displayName: Platform Team
+description: Reliability-oriented defaults for shared platform modules across teams.
+defaultProfile: balanced
+defaultStack: go.md
+defaultBlueprint: go-service.md
+ciGuardrails: true
+lockCi: false
+blockingSeverities: critical, high
+owner: platform-foundation
+lastUpdated: 2026-03-19

package/.agent-context/profiles/regulated.md

@@ -1,13 +1,13 @@
-# Team Profile Pack: Regulated
-
-slug: regulated
-displayName: Regulated Team
-description: Compliance-first defaults with strict policy and locked CI guardrails.
-defaultProfile: strict
-defaultStack: typescript.md
-defaultBlueprint: api-nextjs.md
-ciGuardrails: true
-lockCi: true
-blockingSeverities: critical, high, medium
-owner: governance-office
-lastUpdated: 2026-03-19
+# Team Profile Pack: Regulated
+
+slug: regulated
+displayName: Regulated Team
+description: Compliance-first defaults with strict policy and locked CI guardrails.
+defaultProfile: strict
+defaultStack: typescript.md
+defaultBlueprint: api-nextjs.md
+ciGuardrails: true
+lockCi: true
+blockingSeverities: critical, high, medium
+owner: governance-office
+lastUpdated: 2026-03-19

package/.agent-context/profiles/startup.md

@@ -1,13 +1,13 @@
-# Team Profile Pack: Startup
-
-slug: startup
-displayName: Startup Team
-description: Fast iteration with balanced guardrails and quick onboarding defaults.
-defaultProfile: balanced
-defaultStack: typescript.md
-defaultBlueprint: api-nextjs.md
-ciGuardrails: true
-lockCi: false
-blockingSeverities: critical, high
-owner: product-engineering
-lastUpdated: 2026-03-19
+# Team Profile Pack: Startup
+
+slug: startup
+displayName: Startup Team
+description: Fast iteration with balanced guardrails and quick onboarding defaults.
+defaultProfile: balanced
+defaultStack: typescript.md
+defaultBlueprint: api-nextjs.md
+ciGuardrails: true
+lockCi: false
+blockingSeverities: critical, high
+owner: product-engineering
+lastUpdated: 2026-03-19

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

@@ -22,11 +22,11 @@ For EVERY violation found:
 
 Output format:
 ## PR REVIEW RESULTS
-✅ [Item] — Passes
-❌ [Item] — FAILS (with Reasoning Chain)
+PASS [Item]
+FAIL [Item] (with Reasoning Chain)
 
 ## SECURITY AUDIT RESULTS
-🔴/🟠/🟡/🟢 [Finding] — severity + fix
+CRITICAL/HIGH/MEDIUM/LOW [Finding] — severity + fix
 
 VERDICT: PASS / FAIL
 ```

package/.agent-context/review-checklists/frontend-skill-parity.md

@@ -1,28 +1,28 @@
-# Frontend Skill Parity Checklist
-
-Use this checklist to enforce mandatory frontend parity aligned with benchmark-driven standards from `MiniMax-AI/skills` `frontend-dev` profile.
-
-## Architecture and Composition
-- [ ] Frontend structure follows feature-driven organization.
-- [ ] Smart and dumb component separation is explicit and documented.
-- [ ] Server state and client state boundaries are documented and enforced.
-
-## Interaction and Motion
-- [ ] Primary user journey includes intentional animation without motion overload.
-- [ ] Reduced-motion fallback behavior is implemented and documented.
-- [ ] Transition timing and easing are consistent across key screens.
-
-## Accessibility and Responsiveness
-- [ ] Keyboard navigation works on all critical flows.
-- [ ] Contrast, typography scale, and focus visibility pass baseline checks.
-- [ ] Layout behavior is validated across mobile and desktop breakpoints.
-
-## UX Narrative and Conversion Clarity
-- [ ] Page hierarchy communicates value proposition within first viewport.
-- [ ] Primary calls to action are explicit and consistently placed.
-- [ ] Error and empty states contain actionable guidance.
-
-## Release Evidence
-- [ ] Frontend parity checklist artifact is attached to release evidence.
-- [ ] Frontend usability audit report is attached to release evidence.
-- [ ] Any parity waiver includes owner, expiry, and risk statement.
+# Frontend Skill Parity Checklist
+
+Use this checklist to enforce mandatory frontend parity aligned with benchmark-driven standards from `MiniMax-AI/skills` `frontend-dev` profile.
+
+## Architecture and Composition
+- [ ] Frontend structure follows feature-driven organization.
+- [ ] Smart and dumb component separation is explicit and documented.
+- [ ] Server state and client state boundaries are documented and enforced.
+
+## Interaction and Motion
+- [ ] Primary user journey includes intentional animation without motion overload.
+- [ ] Reduced-motion fallback behavior is implemented and documented.
+- [ ] Transition timing and easing are consistent across key screens.
+
+## Accessibility and Responsiveness
+- [ ] Keyboard navigation works on all critical flows.
+- [ ] Contrast, typography scale, and focus visibility pass baseline checks.
+- [ ] Layout behavior is validated across mobile and desktop breakpoints.
+
+## UX Narrative and Conversion Clarity
+- [ ] Page hierarchy communicates value proposition within first viewport.
+- [ ] Primary calls to action are explicit and consistently placed.
+- [ ] Error and empty states contain actionable guidance.
+
+## Release Evidence
+- [ ] Frontend parity checklist artifact is attached to release evidence.
+- [ ] Frontend usability audit report is attached to release evidence.
+- [ ] Any parity waiver includes owner, expiry, and risk statement.

package/.agent-context/review-checklists/frontend-usability.md

@@ -1,33 +1,33 @@
-# Frontend Usability Checklist — V1.7 Gate
-
-Run this checklist before claiming frontend work is production-ready.
-
-## 1. Visual System
-- [ ] Typography scale is consistent and tokenized.
-- [ ] Color usage follows design tokens and avoids ad-hoc values.
-- [ ] Spacing and layout rhythm is coherent across pages.
-
-## 2. Responsiveness
-- [ ] Core pages are usable at mobile, tablet, and desktop breakpoints.
-- [ ] Navigation remains accessible and understandable on small screens.
-- [ ] No content overlap, clipped text, or horizontal scroll regressions.
-
-## 3. Accessibility
-- [ ] Keyboard-only navigation covers all critical user paths.
-- [ ] Primary text and actionable controls meet WCAG AA contrast.
-- [ ] Reduced-motion mode is respected for non-essential animations.
-
-## 4. Interaction Quality
-- [ ] Motion is meaningful, not decorative noise.
-- [ ] Loading, empty, and error states are explicitly designed.
-- [ ] CTA hierarchy is clear and supports user intent.
-
-## 5. Performance and Stability
-- [ ] Lighthouse mobile performance target is met on core pages.
-- [ ] No severe layout shift during load and transition.
-- [ ] Visual regression checks cover protected pages.
-
-## 6. Documentation and Release Evidence
-- [ ] Frontend architecture decision is documented.
-- [ ] Visual baseline update process is documented.
-- [ ] Release note includes usability and responsiveness evidence.
+# Frontend Usability Checklist — V1.7 Gate
+
+Run this checklist before claiming frontend work is production-ready.
+
+## 1. Visual System
+- [ ] Typography scale is consistent and tokenized.
+- [ ] Color usage follows design tokens and avoids ad-hoc values.
+- [ ] Spacing and layout rhythm is coherent across pages.
+
+## 2. Responsiveness
+- [ ] Core pages are usable at mobile, tablet, and desktop breakpoints.
+- [ ] Navigation remains accessible and understandable on small screens.
+- [ ] No content overlap, clipped text, or horizontal scroll regressions.
+
+## 3. Accessibility
+- [ ] Keyboard-only navigation covers all critical user paths.
+- [ ] Primary text and actionable controls meet WCAG AA contrast.
+- [ ] Reduced-motion mode is respected for non-essential animations.
+
+## 4. Interaction Quality
+- [ ] Motion is meaningful, not decorative noise.
+- [ ] Loading, empty, and error states are explicitly designed.
+- [ ] CTA hierarchy is clear and supports user intent.
+
+## 5. Performance and Stability
+- [ ] Lighthouse mobile performance target is met on core pages.
+- [ ] No severe layout shift during load and transition.
+- [ ] Visual regression checks cover protected pages.
+
+## 6. Documentation and Release Evidence
+- [ ] Frontend architecture decision is documented.
+- [ ] Visual baseline update process is documented.
+- [ ] Release note includes usability and responsiveness evidence.

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

@@ -13,13 +13,13 @@ Output format:
 ## PR REVIEW RESULTS
 ━━━━━━━━━━━━━━━━━━━
 
-✅ [Item] — Passes
-❌ [Item] — FAILS
-   📌 Rule: [rule file + section]
-   ❌ Problem: [specific issue found]
-   ✅ Fix: [what to change]
+PASS [Item]
+FAIL [Item]
+   Rule: [rule file + section]
+   Problem: [specific issue found]
+   Fix: [what to change]
 
-VERDICT: PASS ✅ / FAIL ❌ (X/Y items passed)
+VERDICT: PASS / FAIL (X/Y items passed)
 ```
 
 ---
@@ -95,3 +95,8 @@ VERDICT: PASS ✅ / FAIL ❌ (X/Y items passed)
 - [ ] Complex business logic has comments explaining WHY
 - [ ] Public functions/methods have JSDoc/docstrings
 - [ ] README updated if new setup steps required
+- [ ] No emoji in formal documentation or review summaries
+- [ ] Documentation uses plain English and avoids AI cliches
+- [ ] Performance/quality claims include source and timestamp
+- [ ] Acronyms are expanded on first use
+- [ ] Facts and assumptions are explicitly separated

package/.agent-context/review-checklists/release-operations.md

@@ -1,29 +1,29 @@
-# Release Operations Checklist (V1.8)
-
-Use this checklist before promoting any release tag or package publish operation.
-
-## 1) Versioning and Changelog Integrity
-- `package.json` version is valid semantic version (`x.y.z`).
-- `CHANGELOG.md` has a matching release header for the package version.
-- `docs/roadmap.md` reflects release status and scope for the current milestone.
-
-## 2) Quality Gates and Test Evidence
-- `npm run validate` passes with zero failures.
-- `npm run test` passes on the full suite.
-- Frontend governance gate (`npm run audit:frontend-usability`) passes.
-- Release governance gate (`npm run gate:release`) passes.
-
-## 3) Supply Chain and Compliance Evidence
-- SBOM is generated with `npm run sbom:generate`.
-- CI uploads SBOM artifact for retention and audit traceability.
-- CI uploads release-gate report artifact for each run.
-
-## 4) Security and Override Governance
-- `.agent-override.md` entries have valid `Owner` and `Expiry` metadata.
-- No expired overrides remain active.
-- Any temporary exception has explicit rollback owner and date.
-
-## 5) Publish Readiness
-- Release notes summarize scope, risks, and rollback steps.
-- Required GitHub workflows are green on target commit.
-- Tag and publish command are executed only after all checks pass.
+# Release Operations Checklist (V1.8)
+
+Use this checklist before promoting any release tag or package publish operation.
+
+## 1) Versioning and Changelog Integrity
+- `package.json` version is valid semantic version (`x.y.z`).
+- `CHANGELOG.md` has a matching release header for the package version.
+- `docs/roadmap.md` reflects release status and scope for the current milestone.
+
+## 2) Quality Gates and Test Evidence
+- `npm run validate` passes with zero failures.
+- `npm run test` passes on the full suite.
+- Frontend governance gate (`npm run audit:frontend-usability`) passes.
+- Release governance gate (`npm run gate:release`) passes.
+
+## 3) Supply Chain and Compliance Evidence
+- SBOM is generated with `npm run sbom:generate`.
+- CI uploads SBOM artifact for retention and audit traceability.
+- CI uploads release-gate report artifact for each run.
+
+## 4) Security and Override Governance
+- `.agent-override.md` entries have valid `Owner` and `Expiry` metadata.
+- No expired overrides remain active.
+- Any temporary exception has explicit rollback owner and date.
+
+## 5) Publish Readiness
+- Release notes summarize scope, risks, and rollback steps.
+- Required GitHub workflows are green on target commit.
+- Tag and publish command are executed only after all checks pass.

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

@@ -25,6 +25,40 @@ REQUIRED: Documentation MUST be updated in the SAME commit as the endpoint chang
 
 ---
 
+## Human Writing Standard (Mandatory)
+
+This standard applies to API docs, README updates, release notes, and technical explanations.
+
+### Style Baseline
+1. Write for native English speakers.
+2. Target an 8th-grade reading level.
+3. Use clear, direct, plain language.
+4. Keep sentence rhythm natural with short and medium sentences.
+5. Sound confident, practical, and conversational.
+
+### Required Behavior
+1. Explain decisions the way a competent coworker would explain them out loud.
+2. Cut unnecessary words and remove filler.
+3. Use concrete verbs and everyday phrasing.
+4. Rewrite and reorder content when flow is weak.
+
+### Hard Bans
+1. No emoji in formal artifacts.
+2. No AI cliches: delve, leverage, robust, utilize, seamless.
+3. No inflated, academic, or performative language.
+4. No padding, hedging, or redundant phrasing.
+
+### Critical Controls
+1. Any claim about quality, performance, or reliability must include a measurable source and timestamp.
+2. Expand acronyms on first use, then use terms consistently.
+3. Separate facts from assumptions explicitly.
+4. End major explanations with a clear next action.
+
+### Final Check
+Read the text out loud before shipping. If it sounds robotic, rewrite it.
+
+---
+
 ## Documentation Format: OpenAPI 3.1 (Non-Negotiable)
 
 All APIs produce an OpenAPI 3.1 specification. Not 3.0, not proprietary formats, not "we'll add Swagger later."

package/.agent-context/skills/README.md

@@ -1,63 +1,63 @@
-# Skill Platform
-
-The skill platform is the internal skill system for Agentic-Senior-Core.
-
-## Design Goals
-- Unify skill content from benchmark repositories into one governed platform.
-- Make `advance` the default operating tier.
-- Keep `standard` only as a compatibility fallback.
-- Require evidence, validation, and release gates for every skill pack.
-
-## Tier Model
-
-### standard
-- Compatibility mode only.
-- Minimal guidance.
-- No default status for new work.
-
-### advance
-- Default operating tier.
-- Efficient, opinionated, and production-aware.
-- Used for normal feature delivery.
-
-### expert
-- For complex architecture, integration, and critical refactors.
-- Requires stronger evidence and review depth.
-
-### above
-- For release-critical, cross-domain, or enterprise governance work.
-- Requires full evidence bundle and explicit owner signoff.
-
-## Domain Packs
-- [Frontend](frontend/README.md)
-- [Backend](backend/README.md)
-- [Fullstack](fullstack/README.md)
-- [CLI](cli/README.md)
-- [Distribution](distribution/README.md)
-- [Review Quality](review-quality/README.md)
-
-## Folder Structure
-```text
-.agent-context/skills/
-├── README.md
-├── index.json
-├── frontend/
-├── backend/
-├── fullstack/
-├── cli/
-├── distribution/
-└── review-quality/
-```
-
-Each domain folder has its own README plus topic-level docs so the platform can scale like a curated skills library.
-
-## Benchmark Sources
-- sickn33/antigravity-awesome-skills
-- github/awesome-copilot
-- MiniMax-AI/skills
-
-## Platform Rules
-- Every skill pack must define purpose, inputs, outputs, validation, evidence, and fallback.
-- Every skill pack must state the default tier it targets.
-- Every release must include a skill parity check for the configured tiers.
+# Skill Platform
+
+The skill platform is the internal skill system for Agentic-Senior-Core.
+
+## Design Goals
+- Unify skill content from benchmark repositories into one governed platform.
+- Make `advance` the default operating tier.
+- Keep `standard` only as a compatibility fallback.
+- Require evidence, validation, and release gates for every skill pack.
+
+## Tier Model
+
+### standard
+- Compatibility mode only.
+- Minimal guidance.
+- No default status for new work.
+
+### advance
+- Default operating tier.
+- Efficient, opinionated, and production-aware.
+- Used for normal feature delivery.
+
+### expert
+- For complex architecture, integration, and critical refactors.
+- Requires stronger evidence and review depth.
+
+### above
+- For release-critical, cross-domain, or enterprise governance work.
+- Requires full evidence bundle and explicit owner signoff.
+
+## Domain Packs
+- [Frontend](frontend/README.md)
+- [Backend](backend/README.md)
+- [Fullstack](fullstack/README.md)
+- [CLI](cli/README.md)
+- [Distribution](distribution/README.md)
+- [Review Quality](review-quality/README.md)
+
+## Folder Structure
+```text
+.agent-context/skills/
+├── README.md
+├── index.json
+├── frontend/
+├── backend/
+├── fullstack/
+├── cli/
+├── distribution/
+└── review-quality/
+```
+
+Each domain folder has its own README plus topic-level docs so the platform can scale like a curated skills library.
+
+## Benchmark Sources
+- sickn33/antigravity-awesome-skills
+- github/awesome-copilot
+- MiniMax-AI/skills
+
+## Platform Rules
+- Every skill pack must define purpose, inputs, outputs, validation, evidence, and fallback.
+- Every skill pack must state the default tier it targets.
+- Every release must include a skill parity check for the configured tiers.
 - Every deviation from the default tier must be justified in the evidence bundle.