@ryuenn3123/agentic-senior-core 2.0.0 → 2.0.1

package/.agent-context/state/onboarding-report.json

@@ -1,13 +1,13 @@
 {
-  "cliVersion": "2.0.0",
-  "generatedAt": "2026-04-08T03:56:54.149Z",
+  "cliVersion": "2.0.1",
+  "generatedAt": "2026-04-08T14:58:53.636Z",
   "operationMode": "upgrade",
   "selectedProfile": "beginner",
   "selectedProfilePack": null,
   "selectedStack": "typescript.md",
   "selectedBlueprint": "api-nextjs.md",
   "ciGuardrailsEnabled": true,
-  "setupDurationMs": 86,
+  "setupDurationMs": 106,
   "selectedSkillDomains": [],
   "autoDetection": {
     "recommendedStack": "typescript.md",

package/.cursorrules

@@ -1,7 +1,7 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v2.0.0
-Timestamp: 2026-04-08T03:56:54.094Z
+Generated by Agentic-Senior-Core CLI v2.0.1
+Timestamp: 2026-04-08T14:58:53.570Z
 Selected profile: beginner
 Selected policy file: .agent-context/policies/llm-judge-threshold.json
 

package/.windsurfrules

@@ -1,7 +1,7 @@
 # AGENTIC-SENIOR-CORE DYNAMIC GOVERNANCE RULESET
 
-Generated by Agentic-Senior-Core CLI v2.0.0
-Timestamp: 2026-04-08T03:56:54.094Z
+Generated by Agentic-Senior-Core CLI v2.0.1
+Timestamp: 2026-04-08T14:58:53.570Z
 Selected profile: beginner
 Selected policy file: .agent-context/policies/llm-judge-threshold.json
 

package/README.md

@@ -103,7 +103,7 @@ If you have an existing project and want to infuse it with Staff-level context:
 npx @ryuenn3123/agentic-senior-core init
 ```
 
-Use team defaults (V1.8 track) with profile packs:
+Use team defaults (V2.0 track) with profile packs:
 
 ```bash
 npx @ryuenn3123/agentic-senior-core init --profile-pack startup
@@ -170,7 +170,7 @@ Use the stack that matches the project you are actually starting:
 ### Option 4: Clone and Play
 Want to poke around under the hood? Just clone the repo and `npx @ryuenn3123/agentic-senior-core init` locally. No runtime dependencies needed — everything uses native Node.js!
 
-### Upgrade Existing Governance Packs (V1.8)
+### Upgrade Existing Governance Packs (V1.x to V2.x)
 
 Yes, the upgrade flow still works. Use `--dry-run` first to preview changes, then apply with `--yes` when you are ready.
 
@@ -201,7 +201,8 @@ Our documentation has shifted into dedicated tracks to keep this README light:
 
 ## Core Capabilities
 
-- **Delivery Engine (CLI):** Interactive setup via GitHub source, bootstrap scripts, or `npx` after publish.
+- **Delivery Engine (CLI):** Interactive setup via GitHub source, bootstrap scripts, or `npx` after publish. Supported by a robust transactional installer with rollback protection.
+- **Verified Skill Marketplace:** Distribute and validate plugins securely with automated 4-dimension Trust Scoring and Evidence Bundles constraint validation.
 - **Dynamic Context Compiler:** Merges universal rules + selected stack + selected blueprint + optional CI guardrails into one dense, indexed rule file.
 - **Codebase Intelligence:** `.agent-context/state/` gives architecture/dependency boundaries so the agent understands high-risk areas.
 - **Override System:** `.agent-override.md` allows controlled enterprise exceptions without forking core rules.

package/lib/cli/commands/init.mjs

@@ -142,6 +142,14 @@ export function parseInitArguments(commandArguments) {
 
 export async function runInitCommand(targetDirectoryArgument, initOptions = {}) {
   const resolvedTargetDirectoryPath = path.resolve(targetDirectoryArgument || '.');
+
+  if (resolvedTargetDirectoryPath.toLowerCase() === 'c:\\windows' || resolvedTargetDirectoryPath.toLowerCase() === 'c:\\windows\\system32') {
+    console.error('\n[FATAL] Target directory resolved to a Windows system folder (C:\\Windows).');
+    console.error('If you are running Windows npm from inside WSL, this is caused by cmd.exe lacking UNC path support.');
+    console.error('Please install and use a native Linux Node.js/npm directly inside WSL to setup your project.');
+    process.exit(1);
+  }
+
   const setupStartedAt = Date.now();
   await ensureDirectory(resolvedTargetDirectoryPath);
 

package/lib/cli/commands/rollback.mjs

@@ -15,6 +15,13 @@ export async function runRollbackCommand(commandArguments) {
   }
 
   const resolvedTargetDirectoryPath = path.resolve(targetDirectoryArgument);
+
+  if (resolvedTargetDirectoryPath.toLowerCase() === 'c:\\windows' || resolvedTargetDirectoryPath.toLowerCase() === 'c:\\windows\\system32') {
+    console.error('\n[FATAL] Target directory resolved to a Windows system folder (C:\\Windows).');
+    console.error('If you are running Windows npm from inside WSL, this is caused by cmd.exe lacking UNC path support.');
+    console.error('Please install and use a native Linux Node.js/npm directly inside WSL to setup your project.');
+    process.exit(1);
+  }
   
   try {
       await ensureDirectory(resolvedTargetDirectoryPath);

package/lib/cli/commands/upgrade.mjs

@@ -69,6 +69,14 @@ export function parseUpgradeArguments(commandArguments) {
 
 export async function runUpgradeCommand(targetDirectoryArgument, upgradeOptions = {}) {
   const resolvedTargetDirectoryPath = path.resolve(targetDirectoryArgument || '.');
+
+  if (resolvedTargetDirectoryPath.toLowerCase() === 'c:\\windows' || resolvedTargetDirectoryPath.toLowerCase() === 'c:\\windows\\system32') {
+    console.error('\n[FATAL] Target directory resolved to a Windows system folder (C:\\Windows).');
+    console.error('If you are running Windows npm from inside WSL, this is caused by cmd.exe lacking UNC path support.');
+    console.error('Please install and use a native Linux Node.js/npm directly inside WSL to setup your project.');
+    process.exit(1);
+  }
+
   const setupStartedAt = Date.now();
   await ensureDirectory(resolvedTargetDirectoryPath);
 

package/package.json

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