Merge remote-tracking branch 'origin/main' into main

Landed the complete 5-router command model, unified Jira router, guardrails system, and full public web/book synchronization after resolving merge conflicts by taking the reviewed final state.

Author: mayurpise

.github/workflows/ci.yml

@@ -24,6 +24,9 @@ integrations/copilot/.github/copilot-instructions.md.*
 .claude/teams/
 .claude/tasks.json
 
+# Gemini local session state
+.gemini/
+
 # Dependencies
 node_modules/
 
@@ -49,4 +52,4 @@ docs/context-quality-benchmark.md
 
 INDUSTRY_REVIEW.md
 RECOMMENDATIONS.md
-codebase_researcher.md
+codebase_researcher.md

.github/workflows/skill-review.yml

@@ -0,0 +1,29 @@
+adr
+assist-review
+bughunt
+change
+coverage
+debug
+decompose
+deep-review
+deploy-checklist
+discover
+documentation
+draft
+impact
+implement
+incident-response
+index
+init
+jira-create
+jira-preview
+learn
+new-track
+quick-review
+revert
+review
+standup
+status
+tech-debt
+testing-strategy
+tour

.gitignore

@@ -99,7 +99,7 @@ Each module typically contains some combination of:
 
 ```
 [auth] ──> [database]
-   │            │
+   │ │
    └──> [config] <──┘
             │
       [logging] (shared, no deps)
@@ -130,7 +130,7 @@ When modules form a circular dependency (A → B → A), apply this decision pro
 Before (cycle):
 ```
 [user-service] ──> [notification-service]
-       ↑                    │
+       ↑ │
        └────────────────────┘
 ```
 `user-service` imports `sendNotification` from `notification-service`.
@@ -141,9 +141,9 @@ Analysis: Both modules need user preference data. Extract it.
 After (resolved):
 ```
 [user-preferences] (new - extracted shared concern)
-       ↑         ↑
-       │         │
-[user-service]  [notification-service]
+       ↑ ↑
+       │ │
+[user-service] [notification-service]
        │
        └──> [notification-service]
 ```
@@ -191,11 +191,11 @@ Stories flow through three stages:
 ```
 // Story: [Module/File Name]
 //
-// Input:  [what this module/function receives]
+// Input: [what this module/function receives]
 // Process:
-//   1. [first algorithmic step]
-//   2. [second algorithmic step]
-//   3. [third algorithmic step]
+// 1. [first algorithmic step]
+// 2. [second algorithmic step]
+// 3. [third algorithmic step]
 // Output: [what this module/function produces]
 //
 // Dependencies: [what this module relies on]

available_skills.txt

@@ -96,7 +96,7 @@ Track data transformation through the system:
 ```
 input: { userId: "abc", role: "admin" }
   → after auth middleware (file:line): { userId: "abc", role: "admin", verified: true }
-  → after service layer (file:line): { userId: "abc", role: null }  ← DATA LOST HERE
+  → after service layer (file:line): { userId: "abc", role: null } ← DATA LOST HERE
   → at failure point (file:line): TypeError: cannot read 'role' of null
 ```