@ginkoai/cli 2.4.5 → 2.5.1

package/dist/templates/commands/handoff.md

@@ -0,0 +1,40 @@
+---
+description: Complete session handoff with cleanup, docs, and commit
+---
+
+Prepare a complete session handoff.
+
+**Consider these user comments**: $ARGUMENTS
+Seek clarification if necessary.
+
+**Safety check**: If the system appears to be in a broken state, incomplete work, or if the primary goal hasn't been achieved, call `/vibecheck` to assess whether a handoff is appropriate right now.
+
+1. **Clean up temporary files**:
+   - Remove any test files or temporary scripts
+   - Clean up debug outputs
+   - Check for and remove any .tmp, .log, or test-* files
+
+2. **Update documentation**:
+   - Update BACKLOG.md if features were completed
+   - Check if CLAUDE.md needs updates for new patterns
+   - Note any new architectural decisions
+
+3. **Commit all changes**:
+   - Review all modified files with git status
+   - Stage appropriate changes
+   - Create a descriptive commit message
+
+4. **Generate session handoff**:
+   - Run `ginko handoff "$ARGUMENTS"` to create handoff
+   - The handoff will be saved to `.ginko/sessions/*/current.md`
+   - Previous handoff automatically archived with date and description
+   - AI will self-identify model, version, and provider in frontmatter
+   - Include current branch state and next steps
+
+Make sure to:
+- Verify no secrets or API keys are being committed
+- Ensure all tests pass before committing
+- Leave the codebase in a working state
+- Document any environment changes needed
+
+This ensures a smooth transition for the next session.

package/dist/templates/commands/quick.md

@@ -0,0 +1,27 @@
+---
+description: Execute a quick task without extensive planning or discussion
+---
+
+Execute a quick task efficiently.
+
+**Task requested**: $ARGUMENTS
+Seek clarification only if the task is ambiguous.
+
+For this quick task:
+- Skip extensive planning unless critical
+- Focus on getting it done correctly
+- Minimal output - just essential information
+- No lengthy explanations unless requested
+
+If the task seems complex or risky, call /vibecheck to reassess the approach.
+
+Common quick tasks:
+- Fix a typo
+- Update a version number
+- Add a simple comment
+- Rename a variable
+- Format code
+- Run a single command
+- Check status
+
+Remember: Quick doesn't mean careless. Still follow best practices, just with less ceremony.

package/dist/templates/commands/ship.md

@@ -0,0 +1,43 @@
+---
+description: Create and push a PR-ready branch with all changes
+---
+
+Ship the current work by creating a pull request.
+
+**Consider these user comments**: $ARGUMENTS
+Seek clarification if necessary (e.g., PR title, target branch, urgency).
+
+**Safety check**: If tests are failing, code is incomplete, or there are obvious issues, call `/vibecheck` to assess whether shipping is appropriate right now.
+
+1. **Pre-flight checks**:
+   - Run linting: `npm run lint` (if available)
+   - Run type checking: `npm run typecheck` (if available)
+   - Run tests: `npm test`
+   - Ensure all checks pass
+
+2. **Clean up and commit**:
+   - Review all changes with git diff
+   - Stage all appropriate files
+   - Create atomic, well-described commits
+
+3. **Prepare the branch**:
+   - Ensure branch name follows pattern: feat/*, fix/*, chore/*
+   - Push to remote with -u flag
+   - Set up tracking if needed
+
+4. **Create pull request**:
+   - Use gh pr create
+   - Generate comprehensive PR description from commits
+   - Include test plan
+   - Link any related issues
+   - Add appropriate labels
+
+5. **Post-PR actions**:
+   - Share PR URL with user
+   - Run ginko handoff to document session
+   - Note any deployment considerations
+
+Remember:
+- Never push directly to main/master
+- Always include test plans in PRs
+- Document breaking changes clearly

package/dist/templates/commands/start.md

@@ -0,0 +1,15 @@
+Start a ginko session using the ginko CLI:
+- Run `ginko start --non-interactive` to begin or resume your session
+- Load context from `.ginko/sessions/[user]/current.md`
+- Check `.ginko/context/modules/` for relevant context modules
+- Review any uncommitted handoffs in `.ginko/`
+
+IMPORTANT: Always use `--non-interactive` flag when running ginko start from an AI session.
+This prevents interactive prompts that would hang waiting for human input.
+
+The ginko CLI automatically handles:
+- Session continuity with handoff resumption
+- Context module discovery based on current work
+- Git-native tracking of all session data
+
+This ensures you're synchronized with the team and continuing from where you left off.

package/dist/templates/commands/vibecheck.md

@@ -0,0 +1,36 @@
+---
+description: Quick recalibration check when feeling lost or misaligned
+---
+
+Let's do a quick vibecheck to ensure we're on the right track.
+
+**Your concern:** $ARGUMENTS
+
+**Current Situation Assessment:**
+1. What were we originally trying to achieve?
+2. What have we actually done so far?
+3. Are we solving the right problem?
+
+**Addressing your specific concern:**
+Based on "$ARGUMENTS", let me evaluate:
+- Is this concern valid?
+- How does it affect our current approach?
+- What adjustments might we need?
+
+**Alignment Check:**
+- Is the current approach the simplest solution?
+- Are we overcomplicating things?
+- Have the requirements changed or evolved?
+
+**Course Correction:**
+- Should we continue on the current path?
+- Do we need to pivot to a different approach?
+- Is there a simpler way to achieve the goal?
+
+**Clear Next Steps:**
+Based on this vibecheck and your concern about "$ARGUMENTS", here's what I recommend:
+1. The single most important thing to do next
+2. What success looks like for that step
+3. Any blockers that need addressing first
+
+Remember: A vibecheck is about recalibration, not criticism. It's a tool for productive collaboration and keeping work focused.

package/dist/templates/skills/ginko/SKILL.md

@@ -26,7 +26,7 @@ Execute ginko commands effectively for session management, task tracking, and kn
 
 ### Starting Work
 ```bash
-GINKO_FORCE_TTY=1 ginko start
+ginko start
 ```
 - Shows flow state, work mode, active sprint
 - Displays "Next up" task based on assignment and status
@@ -170,13 +170,6 @@ ginko sprint pause <id>        # Temporarily hold
 | Task | `e{NNN}_s{NN}_t{NN}` | `e016_s03_t01` |
 | Ad-hoc | `adhoc_{YYMMDD}_s{NN}` | `adhoc_260123_s01` |
 
-## Environment Variables
-
-| Variable | Purpose |
-|----------|---------|
-| `GINKO_FORCE_TTY=1` | Force rich output (tables, colors) in Claude Code |
-| `FORCE_COLOR=1` | Force chalk colors (auto-set with GINKO_FORCE_TTY) |
-
 ## Troubleshooting
 
 | Issue | Solution |

package/dist/templates/sprint-template.md

@@ -0,0 +1,273 @@
+# Sprint Creation Template
+
+## AI-Mediated Sprint Creation Guide (EPIC-018)
+
+**For AI Partners:** Use this template to create well-formed sprints with rich task content. Unlike epics (which require extensive planning), sprints are focused work units. Your job is to:
+
+1. **Gather context** from the graph and session
+2. **Clarify intent** through natural conversation
+3. **Generate rich tasks** with WHY-WHAT-HOW structure
+4. **Assess confidence** and trigger inquiry when uncertain
+5. **Create the sprint file** and sync to graph
+
+---
+
+## Step 1: Gather Context
+
+Before asking questions, silently gather relevant context:
+
+```bash
+# Check for related bugs, issues, or prior work
+ginko graph query "<topic from user intent>"
+
+# Check current session context
+# (You already have this from the conversation)
+
+# Check what's in progress
+ginko status
+```
+
+**Synthesize:** What do you already know that's relevant? What patterns, ADRs, or gotchas apply?
+
+---
+
+## Step 2: Clarify Intent
+
+The user has expressed intent (e.g., "fix some dashboard bugs"). Ask **only what you need** to create actionable tasks.
+
+**Key questions (ask naturally, not mechanically):**
+
+1. **Scope:** "Which specific issues are we targeting?" or "I found these dashboard-related items in the graph: [list]. Which are priorities?"
+
+2. **Boundaries:** "Anything explicitly out of scope for this sprint?"
+
+3. **Success criteria:** "How will we know we're done?"
+
+**Stop asking when:**
+- You have enough to create 2-6 concrete tasks
+- User signals readiness ("let's go with that", "sounds good")
+- You're confident (>75%) in task definitions
+
+---
+
+## Step 3: Generate Rich Tasks (WHY-WHAT-HOW)
+
+For each task, generate the full structure:
+
+```markdown
+### {sprint_id}_t{NN}: {Title} ({estimate})
+
+**Status:** [ ] Not Started
+**Priority:** {CRITICAL|HIGH|MEDIUM|LOW}
+**Confidence:** {0-100}%
+
+**Problem:** {WHY - 1-2 sentences on the pain point or motivation}
+
+**Solution:** {WHAT - 1-2 sentences on the desired outcome}
+
+**Approach:** {HOW - 2-3 sentences on implementation strategy}
+
+**Scope:**
+  - Includes: {what's in scope}
+  - Excludes: {what's explicitly out}
+
+**Acceptance Criteria:**
+- [ ] {Specific, testable criterion 1}
+- [ ] {Specific, testable criterion 2}
+- [ ] {Tests pass}
+```
+
+### Confidence Scoring (Critical)
+
+Be honest about your confidence in each task:
+
+| Score | Meaning | Your Action |
+|-------|---------|-------------|
+| 90-100% | Crystal clear, obvious implementation | Proceed |
+| 70-89% | Good clarity, minor assumptions | Note assumptions in Approach |
+| 50-69% | Moderate ambiguity | Flag and ask clarifying question |
+| Below 50% | Significant uncertainty | Stop and discuss with human |
+
+**Philosophy:** Low confidence is a STRENGTH. A score of 60 with honest questions is better than 90 with hidden assumptions.
+
+---
+
+## Step 4: Composite Confidence Check
+
+After generating all tasks, calculate the average confidence.
+
+**If composite confidence < 75%:**
+
+```
+I've drafted the sprint, but my overall confidence is {N}%.
+
+Some tasks need clarification:
+- Task 2: {title} (confidence: {N}%) - {what's unclear}
+- Task 4: {title} (confidence: {N}%) - {what's unclear}
+
+This is a good thing! Better to clarify now than build the wrong thing.
+
+For each flagged task, can you help me understand:
+- {Specific question about Task 2}
+- {Specific question about Task 4}
+
+Or if you'd prefer, I can proceed with my best judgment.
+```
+
+**If composite confidence >= 75%:**
+Present the sprint plan and ask for approval before creating files.
+
+---
+
+## Step 5: Create Sprint File
+
+After approval, create the sprint file.
+
+**Filename:** `docs/sprints/SPRINT-YYYY-MM-{sprint_id}-{slug}.md`
+
+Example: `docs/sprints/SPRINT-2026-02-adhoc_260205_s01-dashboard-fixes.md`
+
+**Generate Sprint ID:**
+- For ad-hoc work: `adhoc_{YYMMDD}_s{NN}` (e.g., `adhoc_260205_s01`)
+- For epic work: `e{NNN}_s{NN}` (e.g., `e018_s02`)
+
+### Sprint File Template
+
+```markdown
+# SPRINT: {Sprint Name}
+
+## Sprint Overview
+
+**Sprint Goal**: {One sentence describing what this sprint achieves}
+**Duration**: {YYYY-MM-DD} to {YYYY-MM-DD}
+**Type**: {Bug Fix|Feature|Infrastructure|Polish}
+**Progress:** 0% (0/{N} tasks complete)
+**ID:** `{sprint_id}`
+
+**Success Criteria:**
+- {Sprint-level success criterion 1}
+- {Sprint-level success criterion 2}
+
+---
+
+## Sprint Tasks
+
+{For each task, use the WHY-WHAT-HOW format from Step 3}
+
+---
+
+## Related Documents
+
+- **Epic**: {Epic name or "Ad-Hoc Work"}
+- **ADRs**: {List relevant ADRs}
+- **Patterns**: {List relevant patterns}
+
+---
+
+**Sprint Status**: Active
+**Start Date**: {YYYY-MM-DD}
+**Created By**: {user email}
+```
+
+---
+
+## Step 6: Sync to Graph
+
+After creating the sprint file:
+
+```bash
+ginko push sprint
+```
+
+Then start the first task:
+
+```bash
+ginko task start {sprint_id}_t01
+```
+
+---
+
+## Content Quality Standards
+
+Tasks are assessed as:
+
+| Quality | Criteria |
+|---------|----------|
+| **Rich** | Has problem, solution, approach, scope, criteria |
+| **Adequate** | Has basics but missing approach or scope |
+| **Thin** | Missing problem or acceptance criteria - needs enrichment |
+
+**Target:** All tasks should be Rich or Adequate. Thin tasks trigger inquiry.
+
+---
+
+## Work Mode Sensitivity
+
+Adjust depth based on signals:
+
+**Hack & Ship** (quick fix, spike, experiment):
+- 1-3 tasks, minimal ceremony
+- Confidence threshold: 60%
+- Skip detailed scope if obvious
+
+**Think & Build** (standard work):
+- 2-6 tasks, full WHY-WHAT-HOW
+- Confidence threshold: 75%
+- Include scope and acceptance criteria
+
+**Full Planning** (complex, multi-person):
+- Detailed task breakdown
+- Confidence threshold: 85%
+- Include dependencies, risks
+
+---
+
+## Example Conversation Flow
+
+**Human:** "Let's start a sprint to fix some dashboard bugs"
+
+**AI:** *[Silently queries: `ginko graph query "dashboard bugs"`]*
+
+**AI:** "I found a few dashboard-related items in the graph:
+- Stale data in Projects tab after rename
+- Member list not refreshing
+- Settings panel layout issue on mobile
+
+Which of these are priorities for this sprint? Any others I missed?"
+
+**Human:** "The first two - they're related. Skip the mobile thing for now."
+
+**AI:** "Got it. Both relate to data freshness after project changes. Let me draft the tasks:
+
+**Sprint: Dashboard Data Refresh Fixes**
+
+1. **Fix member list refresh on project rename** (2h, confidence: 85%)
+   - Problem: Member list shows stale data after project name changes
+   - Solution: Trigger refresh when project name updates
+
+2. **Add loading state during refresh** (1h, confidence: 90%)
+   - Problem: No feedback during data reload
+   - Solution: Show spinner while fetching updated data
+
+3. **Test and verify fixes** (1h, confidence: 95%)
+   - Verify both issues resolved, no regressions
+
+Overall confidence: 90%. Ready to create the sprint?"
+
+**Human:** "Looks good, let's go."
+
+**AI:** *[Creates sprint file, runs `ginko push sprint`, starts first task]*
+
+---
+
+## Key Principles
+
+1. **Context first:** Query the graph before asking questions
+2. **Inquiry is strength:** Low confidence triggers conversation, not silent assumptions
+3. **Rich tasks:** Every task has WHY-WHAT-HOW, not just a title
+4. **Natural conversation:** Don't interrogate - collaborate
+5. **Human approval:** Present plan before creating files
+
+---
+
+**Remember:** The goal is actionable tasks the AI can execute autonomously. Quality thinking over complete forms.

package/dist/utils/cloud-guard.d.ts

@@ -0,0 +1,48 @@
+/**
+ * @fileType: utility
+ * @status: current
+ * @updated: 2026-02-15
+ * @tags: [cloud, auth, guard, local-first, ADR-078]
+ * @related: [auth-storage.ts, identity.ts]
+ * @priority: critical
+ * @complexity: low
+ * @dependencies: [chalk]
+ */
+import { type AuthSession } from './auth-storage.js';
+export interface CloudStatus {
+    /** Whether the user is authenticated with Ginko Cloud */
+    available: boolean;
+    /** The auth session if available, null otherwise */
+    session: AuthSession | null;
+}
+/**
+ * Non-blocking cloud availability check.
+ *
+ * Returns cloud status without blocking command execution.
+ * Use this for LOCAL and CLOUD-ENHANCED commands that should
+ * work without authentication but can do more with it.
+ *
+ * @param _commandName - The command name (for future telemetry)
+ * @returns CloudStatus indicating whether cloud features are available
+ */
+export declare function withOptionalCloud(_commandName: string): Promise<CloudStatus>;
+/**
+ * Blocking cloud requirement check.
+ *
+ * Shows a value-proposition upgrade message and exits cleanly
+ * if the user is not authenticated. Use this for commands that
+ * fundamentally require Ginko Cloud (push, pull, graph, team, etc.).
+ *
+ * @param commandName - The command name for the error message
+ */
+export declare function requireCloud(commandName: string): Promise<void>;
+/**
+ * Show a one-time upgrade hint after successful local command usage.
+ *
+ * Only shown once per CLI process to avoid nagging.
+ * Call this at the end of LOCAL commands to gently surface cloud features.
+ *
+ * @param feature - The cloud feature that would enhance this command
+ */
+export declare function showCloudUpgradeHint(feature: string): Promise<void>;
+//# sourceMappingURL=cloud-guard.d.ts.map

package/dist/utils/cloud-guard.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"cloud-guard.d.ts","sourceRoot":"","sources":["../../src/utils/cloud-guard.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAeH,OAAO,EAAoC,KAAK,WAAW,EAAE,MAAM,mBAAmB,CAAC;AAMvF,MAAM,WAAW,WAAW;IAC1B,yDAAyD;IACzD,SAAS,EAAE,OAAO,CAAC;IACnB,oDAAoD;IACpD,OAAO,EAAE,WAAW,GAAG,IAAI,CAAC;CAC7B;AASD;;;;;;;;;GASG;AACH,wBAAsB,iBAAiB,CAAC,YAAY,EAAE,MAAM,GAAG,OAAO,CAAC,WAAW,CAAC,CAalF;AAMD;;;;;;;;GAQG;AACH,wBAAsB,YAAY,CAAC,WAAW,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC,CAoBrE;AAMD;;;;;;;GAOG;AACH,wBAAsB,oBAAoB,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC,CAWzE"}

package/dist/utils/cloud-guard.js

@@ -0,0 +1,107 @@
+/**
+ * @fileType: utility
+ * @status: current
+ * @updated: 2026-02-15
+ * @tags: [cloud, auth, guard, local-first, ADR-078]
+ * @related: [auth-storage.ts, identity.ts]
+ * @priority: critical
+ * @complexity: low
+ * @dependencies: [chalk]
+ */
+/**
+ * Cloud Guard Utility (ADR-078: Local-First CLI Architecture)
+ *
+ * Provides three tiers of cloud availability checks:
+ *
+ *   LOCAL commands:          Use withOptionalCloud() — works with zero auth
+ *   CLOUD-ENHANCED commands: Use withOptionalCloud() — works locally, richer with cloud
+ *   CLOUD-ONLY commands:     Use requireCloud() — shows upgrade message and exits
+ *
+ * Replaces hard requireAuth() gates that blocked open-source CLI usage.
+ */
+import chalk from 'chalk';
+import { isAuthenticated, loadAuthSession } from './auth-storage.js';
+// Track whether we've shown the upgrade hint this session
+let upgradeHintShown = false;
+// =============================================================================
+// Non-blocking check — for LOCAL + CLOUD-ENHANCED commands
+// =============================================================================
+/**
+ * Non-blocking cloud availability check.
+ *
+ * Returns cloud status without blocking command execution.
+ * Use this for LOCAL and CLOUD-ENHANCED commands that should
+ * work without authentication but can do more with it.
+ *
+ * @param _commandName - The command name (for future telemetry)
+ * @returns CloudStatus indicating whether cloud features are available
+ */
+export async function withOptionalCloud(_commandName) {
+    try {
+        const session = await loadAuthSession();
+        return {
+            available: session !== null,
+            session,
+        };
+    }
+    catch {
+        return {
+            available: false,
+            session: null,
+        };
+    }
+}
+// =============================================================================
+// Blocking gate — for CLOUD-ONLY commands
+// =============================================================================
+/**
+ * Blocking cloud requirement check.
+ *
+ * Shows a value-proposition upgrade message and exits cleanly
+ * if the user is not authenticated. Use this for commands that
+ * fundamentally require Ginko Cloud (push, pull, graph, team, etc.).
+ *
+ * @param commandName - The command name for the error message
+ */
+export async function requireCloud(commandName) {
+    const authenticated = await isAuthenticated();
+    if (!authenticated) {
+        console.log('');
+        console.log(chalk.cyan(`  ginko ${commandName}`) + chalk.dim(' requires Ginko Cloud.'));
+        console.log('');
+        console.log(chalk.white('  Ginko Cloud adds:'));
+        console.log(chalk.dim('    - Knowledge graph search across your codebase'));
+        console.log(chalk.dim('    - Team collaboration and visibility'));
+        console.log(chalk.dim('    - AI-powered coaching insights'));
+        console.log('');
+        console.log(chalk.white('  Get started: ') + chalk.cyan('ginko login'));
+        console.log(chalk.dim('  Learn more:  https://ginkoai.com/cloud'));
+        console.log('');
+        console.log(chalk.dim('  Everything you\'ve built locally will sync when you connect.'));
+        console.log('');
+        process.exit(0);
+    }
+}
+// =============================================================================
+// End-of-session nudge — shown once per session
+// =============================================================================
+/**
+ * Show a one-time upgrade hint after successful local command usage.
+ *
+ * Only shown once per CLI process to avoid nagging.
+ * Call this at the end of LOCAL commands to gently surface cloud features.
+ *
+ * @param feature - The cloud feature that would enhance this command
+ */
+export async function showCloudUpgradeHint(feature) {
+    if (upgradeHintShown)
+        return;
+    const authenticated = await isAuthenticated();
+    if (authenticated)
+        return;
+    upgradeHintShown = true;
+    console.log('');
+    console.log(chalk.dim(`  Tip: ${feature}`));
+    console.log(chalk.dim('  Connect with: ginko login'));
+}
+//# sourceMappingURL=cloud-guard.js.map

package/dist/utils/cloud-guard.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"cloud-guard.js","sourceRoot":"","sources":["../../src/utils/cloud-guard.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH;;;;;;;;;;GAUG;AAEH,OAAO,KAAK,MAAM,OAAO,CAAC;AAC1B,OAAO,EAAE,eAAe,EAAE,eAAe,EAAoB,MAAM,mBAAmB,CAAC;AAavF,0DAA0D;AAC1D,IAAI,gBAAgB,GAAG,KAAK,CAAC;AAE7B,gFAAgF;AAChF,2DAA2D;AAC3D,gFAAgF;AAEhF;;;;;;;;;GASG;AACH,MAAM,CAAC,KAAK,UAAU,iBAAiB,CAAC,YAAoB;IAC1D,IAAI,CAAC;QACH,MAAM,OAAO,GAAG,MAAM,eAAe,EAAE,CAAC;QACxC,OAAO;YACL,SAAS,EAAE,OAAO,KAAK,IAAI;YAC3B,OAAO;SACR,CAAC;IACJ,CAAC;IAAC,MAAM,CAAC;QACP,OAAO;YACL,SAAS,EAAE,KAAK;YAChB,OAAO,EAAE,IAAI;SACd,CAAC;IACJ,CAAC;AACH,CAAC;AAED,gFAAgF;AAChF,0CAA0C;AAC1C,gFAAgF;AAEhF;;;;;;;;GAQG;AACH,MAAM,CAAC,KAAK,UAAU,YAAY,CAAC,WAAmB;IACpD,MAAM,aAAa,GAAG,MAAM,eAAe,EAAE,CAAC;IAE9C,IAAI,CAAC,aAAa,EAAE,CAAC;QACnB,OAAO,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;QAChB,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,WAAW,WAAW,EAAE,CAAC,GAAG,KAAK,CAAC,GAAG,CAAC,wBAAwB,CAAC,CAAC,CAAC;QACxF,OAAO,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;QAChB,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,KAAK,CAAC,qBAAqB,CAAC,CAAC,CAAC;QAChD,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,GAAG,CAAC,mDAAmD,CAAC,CAAC,CAAC;QAC5E,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,GAAG,CAAC,yCAAyC,CAAC,CAAC,CAAC;QAClE,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,GAAG,CAAC,oCAAoC,CAAC,CAAC,CAAC;QAC7D,OAAO,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;QAChB,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,KAAK,CAAC,iBAAiB,CAAC,GAAG,KAAK,CAAC,IAAI,CAAC,aAAa,CAAC,CAAC,CAAC;QACxE,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,GAAG,CAAC,0CAA0C,CAAC,CAAC,CAAC;QACnE,OAAO,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;QAChB,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,GAAG,CAAC,gEAAgE,CAAC,CAAC,CAAC;QACzF,OAAO,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;QAEhB,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAClB,CAAC;AACH,CAAC;AAED,gFAAgF;AAChF,gDAAgD;AAChD,gFAAgF;AAEhF;;;;;;;GAOG;AACH,MAAM,CAAC,KAAK,UAAU,oBAAoB,CAAC,OAAe;IACxD,IAAI,gBAAgB;QAAE,OAAO;IAE7B,MAAM,aAAa,GAAG,MAAM,eAAe,EAAE,CAAC;IAC9C,IAAI,aAAa;QAAE,OAAO;IAE1B,gBAAgB,GAAG,IAAI,CAAC;IAExB,OAAO,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;IAChB,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,GAAG,CAAC,UAAU,OAAO,EAAE,CAAC,CAAC,CAAC;IAC5C,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,GAAG,CAAC,6BAA6B,CAAC,CAAC,CAAC;AACxD,CAAC"}

package/dist/utils/config-loader.d.ts

@@ -36,11 +36,11 @@ export declare function loadLocalConfig(): Promise<LocalConfig>;
  * @example
  * // Using path key
  * const sprintPath = await resolveProjectPath('currentSprint');
- * // → /Users/cnorton/Development/ginko/docs/sprints/CURRENT-SPRINT.md
+ * // → /home/user/my-project/docs/sprints/CURRENT-SPRINT.md
  *
  * // Using relative path directly
  * const customPath = await resolveProjectPath('docs/custom/file.md');
- * // → /Users/cnorton/Development/ginko/docs/custom/file.md
+ * // → /home/user/my-project/docs/custom/file.md
  */
 export declare function resolveProjectPath(relativePath: string): Promise<string>;
 /**

package/dist/utils/config-loader.js

@@ -187,11 +187,11 @@ async function createLocalConfig(projectRoot) {
  * @example
  * // Using path key
  * const sprintPath = await resolveProjectPath('currentSprint');
- * // → /Users/cnorton/Development/ginko/docs/sprints/CURRENT-SPRINT.md
+ * // → /home/user/my-project/docs/sprints/CURRENT-SPRINT.md
  *
  * // Using relative path directly
  * const customPath = await resolveProjectPath('docs/custom/file.md');
- * // → /Users/cnorton/Development/ginko/docs/custom/file.md
+ * // → /home/user/my-project/docs/custom/file.md
  */
 export async function resolveProjectPath(relativePath) {
     const [localConfig, projectConfig] = await Promise.all([

package/dist/utils/helpers.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"helpers.d.ts","sourceRoot":"","sources":["../../src/utils/helpers.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAOH,wBAAsB,WAAW,IAAI,OAAO,CAAC,MAAM,CAAC,CAGnD;AAED,wBAAsB,cAAc,IAAI,OAAO,CAAC,MAAM,CAAC,CAEtD;AAED,wBAAsB,YAAY,IAAI,OAAO,CAAC,MAAM,CAAC,CAmBpD;AAED,wBAAgB,aAAa,CAAC,IAAI,EAAE,IAAI,GAAG,MAAM,CAWhD;AAED,wBAAsB,cAAc,CAAC,SAAS,EAAE,GAAG,GAAG,OAAO,CAAC,MAAM,CAAC,CAkBpE;AAED,wBAAsB,cAAc,IAAI,OAAO,CAAC;IAC9C,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,QAAQ,EAAE,MAAM,CAAC;CAClB,CAAC,CAqCD"}
+{"version":3,"file":"helpers.d.ts","sourceRoot":"","sources":["../../src/utils/helpers.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAOH,wBAAsB,WAAW,IAAI,OAAO,CAAC,MAAM,CAAC,CAGnD;AAED,wBAAsB,cAAc,IAAI,OAAO,CAAC,MAAM,CAAC,CAEtD;AAED,wBAAsB,YAAY,IAAI,OAAO,CAAC,MAAM,CAAC,CAoBpD;AAED,wBAAgB,aAAa,CAAC,IAAI,EAAE,IAAI,GAAG,MAAM,CAWhD;AAED,wBAAsB,cAAc,CAAC,SAAS,EAAE,GAAG,GAAG,OAAO,CAAC,MAAM,CAAC,CAkBpE;AAED,wBAAsB,cAAc,IAAI,OAAO,CAAC;IAC9C,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,QAAQ,EAAE,MAAM,CAAC;CAClB,CAAC,CAqCD"}