work-chronicler 0.2.2 → 0.3.1

package/.agent/skills/work-chronicler-detect-projects/SKILL.md

@@ -57,6 +57,17 @@ Analyze work history to identify major projects and group related work.
    - Consider temporal clustering (work in same 2-4 week period)
    - Use PR labels and repository patterns
 
+## Output Location
+
+**IMPORTANT:** You must do BOTH of the following:
+
+1. **Respond in-thread** with the project summary (for immediate feedback and MCP integration)
+2. **Save to file**: `<profile-root>/outputs/projects-detected-YYYY-MM-DD.md`
+
+Get the profile root with: `work-chronicler workspace root`
+
+This ensures users have both immediate feedback AND a persistent file they can reference later.
+
 ## Project Summary Format
 
 For each project, gather:

package/.agent/skills/work-chronicler-detect-themes/SKILL.md

@@ -77,6 +77,17 @@ Work data is stored in the workspace work-log directory:
    - PR titles and descriptions keywords
    - Timeline trends (what themes emerged when?)
 
+## Output Location
+
+**IMPORTANT:** You must do BOTH of the following:
+
+1. **Respond in-thread** with the themes analysis (for immediate feedback and MCP integration)
+2. **Save to file**: `<profile-root>/outputs/themes-detected-YYYY-MM-DD.md`
+
+Get the profile root with: `work-chronicler workspace root`
+
+This ensures users have both immediate feedback AND a persistent file they can reference later.
+
 ## Output Format
 
 ```markdown

package/.agent/skills/work-chronicler-generate-resume-bullets/SKILL.md

@@ -66,7 +66,14 @@ Work data is stored in the workspace work-log directory:
 
 ## Output Location
 
-Save generated documents to `generated/resume-bullets-YYYY-MM-DD.md` in the workspace root.
+**IMPORTANT:** You must do BOTH of the following:
+
+1. **Respond in-thread** with the resume bullets (for immediate feedback and MCP integration)
+2. **Save to file**: `<profile-root>/outputs/resume-bullets-YYYY-MM-DD.md`
+
+Get the profile root with: `work-chronicler workspace root`
+
+This ensures users have both immediate feedback AND a persistent file they can reference later.
 
 ## Bullet Point Format
 

package/.agent/skills/work-chronicler-mgmt-write-peer-review/skill.md

@@ -0,0 +1,469 @@
+---
+name: work-chronicler-mgmt-write-peer-review
+description: Write peer reviews for colleagues. Use when writing peer feedback, 360 reviews, or colleague evaluations. Supports both evidence-based reviews (with work-log data) and narrative reviews (notes-only).
+user-invocable: true
+disable-model-invocation: true
+---
+
+# Write Peer Review
+
+Write peer reviews for colleagues. Adapts to available data - works with full work-log evidence or just manager/peer notes.
+
+## Quick Review vs Full Mode
+
+**Quick mode** (no report needed):
+- For one-off peer reviews
+- Interactive questions only (no work-log data or supporting documents)
+- Saves to `outputs/peer-review-{name}-{date}.md` in your current profile
+- Works in any profile (IC or manager mode)
+
+**Full mode** (with report):
+- Track peer over time with notes, work-log, past reviews
+- **Requires manager mode and adding them as a report** (even if they don't report to you)
+- Saves to `reports/{report-id}/outputs/peer-review-{date}.md`
+- Use this if you want to:
+  - Reference their work-log data (PRs, tickets)
+  - Add notes about them over time
+  - Include past peer reviews or performance reviews
+  - Build evidence-based reviews with specific examples
+
+> **Important:** If you want to use work-log data or additional supporting artifacts (notes, past reviews, etc.), you MUST add them as a report in manager mode. Quick mode is interactive-only with no data references.
+
+## Workspace
+
+**Active profile:** !`work-chronicler workspace profile`
+**Manager root:** !`work-chronicler workspace root`
+
+> **For non-Claude tools:** Run `work-chronicler workspace root` to get your manager profile path.
+
+## User Input
+
+**Optional:**
+- **Report ID**: The kebab-case identifier if using full mode (e.g., "alice-smith")
+  - See available reports: `work-chronicler reports list`
+  - If not provided, skill will ask if this is a quick review or if you want to add them as a report
+
+**Also Optional:**
+- **Review period**: Time range if relevant (e.g., "Q4 2025", "2025 annual")
+- **Review template**: Company-specific questions or format to follow
+- **Focus areas**: Specific themes, projects, or competencies to address
+
+**Example invocations:**
+
+*Full mode (with report):*
+- `/work-chronicler-mgmt-write-peer-review alice-smith`
+- `/work-chronicler-mgmt-write-peer-review bob-jones Q4-2025`
+
+*Quick mode (no report):*
+- `/work-chronicler-mgmt-write-peer-review` → Will ask if quick review or add report
+
+**When user provides a template:**
+
+If the template includes structured rating questions (e.g., "Rarely/Sometimes/Consistently"), automatically offer interactive mode:
+
+> "I see your template has rating questions. Would you like me to guide you through each question interactively, collect your answers, and synthesize them into a polished narrative review?"
+
+If they say yes, proceed to Interactive Mode (step 3a in Instructions).
+If they say no, use the template as-is and ask them to provide their overall thoughts.
+
+**Template parsing:**
+- Extract all competency statements (e.g., "They easily adapt to change")
+- Note the rating scale (Rarely/Sometimes/Consistently, or Poor/Good/Excellent, etc.)
+- Identify any open-ended questions at the end
+- Preserve any company-specific sections or requirements
+
+## Data Location
+
+**Quick mode** (no supporting data):
+```
+<profile-root>/
+└── outputs/                   # Generated peer reviews
+    └── peer-review-{name}-{date}.md
+```
+
+**Full mode** (with report in manager mode):
+```
+<manager-root>/
+└── reports/
+    └── <report-id>/
+        ├── work-log/              # Optional - may not exist for peers
+        │   ├── pull-requests/     # Evidence if available
+        │   └── jira/              # Evidence if available
+        ├── analysis/              # Optional - only if work-log exists
+        │   ├── stats.json
+        │   ├── projects.json
+        │   └── timeline.json
+        ├── notes/                 # IMPORTANT: Your observations and collaboration notes
+        ├── peer-reviews/          # Optional: Feedback from others about this person
+        ├── performance-reviews/   # Optional: Past reviews for context
+        └── outputs/               # Generated peer reviews
+```
+
+## Instructions
+
+1. **Determine mode (quick vs full)**:
+
+   **If user provided a report ID:**
+   - Validate it exists in manager config
+   - Use exact report ID provided by user
+   - If invalid, show available reports via `work-chronicler reports list`
+   - Proceed with full mode (skip to step 2)
+
+   **If NO report ID provided:**
+
+   Ask the user:
+   > "Is this a quick peer review, or would you like to add them as a report to track over time?"
+
+   **If they choose "Quick peer review":**
+   - Ask: "What is the person's name?"
+   - Store name for output filename (convert to kebab-case: "Alice Smith" → "alice-smith")
+   - Skip to step 2 (no data to check, will use interactive mode only)
+   - **Save location:** `<profile-root>/outputs/peer-review-{name}-{date}.md`
+
+   **If they choose "Add as report":**
+   - Explain: "Adding them as a report lets you track work-log data, notes, and past reviews for evidence-based peer reviews. Even if they don't report to you, this is how you include supporting data."
+   - Show them: "To add them as a report, run these commands:"
+     ```bash
+     work-chronicler init --mode manager  # If not already in manager mode
+     work-chronicler reports add <their-id> --skip-fetch
+
+     # Then optionally add supporting data:
+     # - Add notes: reports/<their-id>/notes/observations.md
+     # - Fetch their PRs: work-chronicler fetch github --report <their-id>
+     # - Fetch their tickets: work-chronicler fetch jira --report <their-id>
+     ```
+   - Ask: "Have you added them as a report? If so, what's the report ID?"
+   - If they provide ID, validate and proceed with full mode
+   - If they say no, offer to continue with quick mode instead
+
+2. **Ask about template FIRST**:
+
+   ⚠️ **ALWAYS start by asking this question:**
+
+   > "Does your company provide a peer review template or specific questions you need to answer? If so, please paste it now."
+
+   **If they provide a template:**
+   - Parse it for structured rating questions (Rarely/Sometimes/Consistently, etc.)
+   - Note any open-ended questions
+   - Preserve company-specific format requirements
+   - Proceed to step 3 with template context
+
+   **If they say no template:**
+   - Use standard competency questions (defined in step 4a)
+   - Proceed to step 3
+
+3. **Check what data is available** (full mode only, skip in quick mode):
+
+   **If quick mode:**
+   - Skip this step - no data to check
+   - Proceed directly to step 2 (ask about template)
+
+   **If full mode (with report):**
+   - Look for `work-log/pull-requests/` and `work-log/jira/` directories
+   - Check if `analysis/` exists
+   - Always check `notes/` directory (critical for peer reviews)
+   - Check `peer-reviews/` and `performance-reviews/` for additional context
+
+4. **Determine review mode**:
+
+   **If user provided a template with structured questions:**
+   - Ask: "Would you like to answer these questions interactively, or provide your own notes?"
+   - If interactive → proceed to Interactive Mode (step 4a)
+   - If notes → skip to step 5
+
+   **If minimal/no notes and no template:**
+   - Suggest interactive mode: "I don't see many notes. Would you like me to guide you through some peer review questions?"
+   - Offer to use standard competency questions (see below)
+
+4a. **Interactive Mode** (when selected):
+
+   **Common template format** (example):
+   ```
+   They easily adapt to change.
+   □ Rarely  □ Sometimes  □ Consistently
+
+   They welcome perspectives different from their own.
+   □ Rarely  □ Sometimes  □ Consistently
+
+   They commit to tasks and see them through to completion.
+   □ Rarely  □ Sometimes  □ Consistently
+
+   [etc.]
+
+   Additional feedback: [open text field]
+   ```
+
+   **For each question/competency:**
+
+   1. **Present the competency statement**
+      - Example: "They easily adapt to change"
+
+   2. **Ask for the rating**
+      - "How would you rate this? (Rarely / Sometimes / Consistently)"
+      - Accept their response
+
+   3. **Ask for context/examples**
+      - "Would you like to share specific examples or context for this rating?"
+      - If they say yes, collect their examples
+      - If they say no or their answer is vague, prompt: "Can you think of a specific situation that illustrates this?"
+
+   4. **Move to next question**
+      - Repeat for all competencies in template
+
+   5. **Ask for additional open feedback**
+      - "Is there anything else you'd like to mention about working with [Name]?"
+      - "Any other strengths or growth areas to highlight?"
+
+   **Standard competency questions** (use if no template provided):
+   - "They adapt to change" (Rarely/Sometimes/Consistently) + Examples?
+   - "They welcome different perspectives" (Rarely/Sometimes/Consistently) + Examples?
+   - "They commit to tasks and see them through" (Rarely/Sometimes/Consistently) + Examples?
+   - "They are open to feedback" (Rarely/Sometimes/Consistently) + Examples?
+   - "They take initiative" (Rarely/Sometimes/Consistently) + Examples?
+   - "They communicate effectively" (Rarely/Sometimes/Consistently) + Examples?
+   - "They demonstrate technical excellence" (Rarely/Sometimes/Consistently) + Examples?
+
+   **After gathering all answers:**
+
+   **DO NOT** output a bullet list of ratings. Instead:
+
+   1. **Synthesize into narrative prose**
+      - Convert ratings and examples into natural paragraphs
+      - Group related competencies together
+      - Use their specific examples as evidence
+
+   2. **Example synthesis:**
+
+      ❌ **Bad (don't do this):**
+      ```
+      - Adapts to change: Consistently
+      - Welcomes different perspectives: Sometimes
+      - Commits to tasks: Consistently
+      ```
+
+      ✅ **Good (do this):**
+      ```
+      Alice demonstrates strong adaptability and commitment to her work.
+      She consistently adapts to change - for example, when we pivoted
+      the auth migration approach mid-sprint, she quickly adjusted her
+      implementation and helped the team understand the new direction.
+      She also commits fully to tasks and sees them through; I've never
+      seen her drop a commitment, even when priorities shift.
+
+      In terms of collaboration, Alice sometimes struggles to welcome
+      perspectives different from her own. During design reviews, I've
+      noticed she can be defensive about her approach initially, though
+      she generally comes around after discussion. This is an area where
+      continued growth would strengthen her impact on the team.
+      ```
+
+   3. **Organization tips:**
+      - Group "Consistently" items together as strengths
+      - Address "Sometimes" or "Rarely" items as growth opportunities
+      - Use their specific examples to make it concrete
+      - Balance positive and constructive feedback
+      - Write in first person ("I've observed", "In my experience working with them")
+
+5. **Read supporting documents** (critical context):
+   - `notes/` - YOUR observations about working with this person
+   - `peer-reviews/` - What others have said about them
+   - `performance-reviews/` - Past review language and format (if available)
+
+6. **Adapt approach based on available data**:
+
+   **If quick mode (no data):**
+   - Use interactive mode exclusively
+   - Rely entirely on template questions or standard competencies
+   - Synthesize user's responses into prose
+
+   **If full mode with work-log data:**
+   - Read `analysis/stats.json`, `projects.json`, `timeline.json`
+   - Focus on flagship and major impact work
+   - Cross-reference with notes for collaboration context
+   - Use evidence-based structure (see below)
+
+   **If full mode with only notes:**
+   - Focus entirely on qualitative observations from notes
+   - Organize by themes from notes
+   - Supplement with interactive questions if notes are minimal
+   - Use narrative structure (see below)
+
+7. **Structure the review**:
+
+   **Evidence-based format** (when work-log exists):
+   ```markdown
+   # Peer Review: [Name]
+   **Review Period:** [Period]
+   **Reviewed by:** [Your name from context]
+   **Date:** [Current date]
+
+   ## Summary
+   [2-3 sentences on overall collaboration and impact]
+
+   ### Technical Contributions
+   - **[Project/Area]**: [What they did, impact, your observations]
+   - **[Project/Area]**: [What they did, impact, your observations]
+
+   ### Collaboration & Communication
+   - [How they work with others]
+   - [Communication effectiveness]
+   - [Cross-team work examples]
+
+   ### Strengths
+   - [What they excel at]
+   - [Skills that stand out]
+
+   ### Growth Opportunities
+   - [Areas for development]
+   - [Constructive feedback]
+   ```
+
+   **Narrative format** (when only notes exist):
+   ```markdown
+   # Peer Review: [Name]
+   **Review Period:** [Period]
+   **Reviewed by:** [Your name from context]
+   **Date:** [Current date]
+
+   ## Summary
+   [2-3 sentences on your working relationship and overall assessment]
+
+   ### What I've Observed
+
+   #### Strengths
+   - [Specific observations from notes]
+   - [Examples of excellent work or collaboration]
+
+   #### Areas of Impact
+   - [Projects or areas where they've made a difference]
+   - [How they've helped you or the team]
+
+   #### Collaboration Style
+   - [How they communicate]
+   - [How they work with others]
+   - [Team dynamics]
+
+   ### Constructive Feedback
+   - [Growth areas]
+   - [Development opportunities]
+
+   ### Overall Assessment
+   [Final thoughts on working with this person]
+   ```
+
+   **Interactive mode format** (synthesized from template questions):
+   ```markdown
+   # Peer Review: [Name]
+   **Review Period:** [Period]
+   **Reviewed by:** [Your name from context]
+   **Date:** [Current date]
+
+   ## Summary
+   [2-3 sentences highlighting key strengths and overall impression]
+
+   ## Work Style & Collaboration
+
+   [Synthesized narrative from "adapt to change", "welcome perspectives",
+   "open to feedback" responses. Group "Consistently" ratings together as
+   strengths, weave in specific examples provided during interactive mode]
+
+   Example:
+   Alice consistently demonstrates strong adaptability and openness to
+   feedback. When we pivoted our auth migration approach mid-sprint, she
+   quickly adjusted her implementation without complaint and helped onboard
+   others to the new direction. She's also receptive to feedback - during
+   code reviews, I've seen her thoughtfully incorporate suggestions and
+   explain her reasoning when she disagrees, leading to better outcomes.
+
+   ## Reliability & Initiative
+
+   [Synthesized narrative from "commit to tasks", "take initiative"
+   responses]
+
+   Example:
+   I can consistently count on Alice to follow through on commitments. She
+   takes initiative when problems arise - for instance, when we discovered
+   a security gap in our API, she proactively researched solutions and
+   presented options to the team before being asked.
+
+   ## Areas for Growth
+
+   [Synthesized narrative from "Sometimes" or "Rarely" ratings, with
+   constructive framing and specific examples]
+
+   Example:
+   One area where Alice could grow is in welcoming perspectives different
+   from her own. During design discussions, I've noticed she can initially
+   be defensive about her approach, though she generally comes around after
+   further discussion. Actively seeking out alternative viewpoints earlier
+   in the process could strengthen her designs and team collaboration.
+
+   ## Additional Feedback
+
+   [Any open-ended thoughts provided during interactive mode]
+   ```
+
+8. **Template adaptation**:
+   - If user provided a template (from step 2), use that structure exactly
+   - Map available data and interactive responses to template questions
+   - Note where you don't have information to answer specific questions
+
+## Output Location
+
+**Quick mode** (no report ID):
+```
+<profile-root>/outputs/peer-review-{name}-YYYY-MM-DD.md
+```
+
+Example: `~/.work-chronicler/profiles/default/outputs/peer-review-alice-smith-2026-02-13.md`
+
+Use the person's name in kebab-case (e.g., "Alice Smith" → "alice-smith").
+
+**Full mode** (with report ID):
+```
+<manager-root>/reports/<report-id>/outputs/peer-review-YYYY-MM-DD.md
+```
+
+Example: `~/.work-chronicler/profiles/manager/reports/alice-smith/outputs/peer-review-2026-02-13.md`
+
+Use the exact report ID in the path.
+
+**Important:** Ensure the document clearly indicates this is PEER REVIEW feedback:
+- Filename must include `peer-review-` prefix (and person's name in quick mode)
+- Document title should say "Peer Review" or "Peer Feedback"
+- Use first-person language ("I observed", "Working with them")
+- This distinguishes it from manager performance reviews
+
+## Important Constraints
+
+- ✅ Be specific and honest
+- ✅ Balance positive feedback with constructive growth areas
+- ✅ Focus on observable behaviors and outcomes
+- ❌ No rankings or numerical scores
+- ❌ No comparisons with other team members
+- ❌ Don't make up evidence - only cite what you have
+
+## Tips
+
+- **If notes are minimal**: Ask the user if they want to add more observations before generating
+- **For evidence-based reviews**: Connect code contributions to team/business impact
+- **For narrative reviews**: Use specific examples from notes rather than vague praise
+- **Tone**: Professional but authentic - this is peer feedback, not a formal manager review
+- **Balance**: Include both strengths and growth areas in every review
+- **Be specific**: "Great communicator" is weak; "Proactively documented the auth migration in Confluence, making it easy for others to contribute" is strong
+- **Use first person**: "I observed...", "Working with them on...", "I appreciated..."
+
+## Adding Notes Before Generating
+
+If you don't have enough notes to write a meaningful review, suggest the user add observations first:
+
+```bash
+# Create a notes file
+echo "Observations about Alice:
+- Led the auth migration, clear communication
+- Great at explaining complex systems
+- Sometimes moves too fast, could involve team more in decisions
+" > reports/alice-smith/notes/collaboration.md
+```
+
+Then re-run the skill.

package/.agent/skills/work-chronicler-summarize-work/SKILL.md

@@ -65,6 +65,17 @@ Generate a summary including:
 - **Timeline**: Busiest periods, activity trends
 - **Notable Contributions**: Largest PRs, most complex changes
 
+## Output Location
+
+**IMPORTANT:** You must do BOTH of the following:
+
+1. **Respond in-thread** with the work summary (for immediate feedback and MCP integration)
+2. **Save to file**: `<profile-root>/outputs/work-summary-YYYY-MM-DD.md`
+
+Get the profile root with: `work-chronicler workspace root`
+
+This ensures users have both immediate feedback AND a persistent file they can reference later.
+
 ## Example Output
 
 ```markdown

package/.agent/skills/work-chronicler-update-resume/SKILL.md

@@ -104,7 +104,14 @@ Work data is stored in the workspace work-log directory:
 
 ## Output Location
 
-Save generated documents to `generated/resume-updated-YYYY-MM-DD.md` in the workspace root.
+**IMPORTANT:** You must do BOTH of the following:
+
+1. **Respond in-thread** with the resume updates (for immediate feedback and MCP integration)
+2. **Save to file**: `<profile-root>/outputs/resume-updated-YYYY-MM-DD.md`
+
+Get the profile root with: `work-chronicler workspace root`
+
+This ensures users have both immediate feedback AND a persistent file they can reference later.
 
 ## Output Format
 

package/.agent/skills/work-chronicler-write-self-review/SKILL.md

@@ -75,7 +75,14 @@ Work data is stored in the workspace work-log directory:
 
 ## Output Location
 
-Save generated documents to `generated/self-review-YYYY-MM-DD.md` in the workspace root.
+**IMPORTANT:** You must do BOTH of the following:
+
+1. **Respond in-thread** with the self-review (for immediate feedback and MCP integration)
+2. **Save to file**: `<profile-root>/outputs/self-review-YYYY-MM-DD.md`
+
+Get the profile root with: `work-chronicler workspace root`
+
+This ensures users have both immediate feedback AND a persistent file they can reference later.
 
 ## Output Format
 

package/README.md

@@ -17,7 +17,9 @@ But you didn't take notes, and now you're scrolling through months of PRs trying
 
 ### For Managers
 
-Manager mode extends work-chronicler for people managers tracking multiple direct reports. Collect work history for your team, generate evidence-based performance reviews, and maintain team visibility across projects. See the [Manager Mode Guide](docs/manager-mode.md) for details.
+Manager mode extends work-chronicler for people managers tracking multiple direct reports. Collect work history for your team, generate evidence-based performance reviews, and maintain team visibility across projects.
+
+**📚 See the [Manager Mode Guide](documentation/manager-mode.md) for complete documentation.**
 
 ## Quick Start
 
@@ -273,7 +275,15 @@ See [work-chronicler.example.yaml](work-chronicler.example.yaml) for a complete
 
 ### GitHub Token
 
-Create a personal access token at https://github.com/settings/tokens with the `repo` scope (or `public_repo` for public repos only).
+Create a personal access token at https://github.com/settings/tokens with the following scopes:
+
+**Required:**
+- `repo` (for private repos) or `public_repo` (for public repos only)
+
+**Required for auto-discovery with organizations:**
+- `read:org` - Needed to query organization repositories during `init` auto-discovery
+
+Without `read:org`, you can still use work-chronicler by entering repos manually during setup.
 
 ### JIRA Token
 
@@ -327,9 +337,12 @@ After installation, these skills are available as slash commands in your AI codi
 | Skill | Description |
 |-------|-------------|
 | `/work-chronicler-mgmt-write-review-packet` | Generate evidence-based performance review for a direct report |
+| `/work-chronicler-mgmt-write-peer-review` | Write peer reviews for colleagues (works with or without work-log data) |
 | `/work-chronicler-mgmt-quarterly-highlights` | Create concise quarterly summary for 1:1s and calibration |
 | `/work-chronicler-mgmt-team-summary` | Generate team-level overview for leadership and calibration |
 
+**📚 For detailed skill documentation, see [Available Skills Guide](documentation/available-skills.md)**
+
 ### Supported AI Tools
 
 Skills can be installed to:

package/dist/cli/commands/fetch/all.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"all.d.ts","sourceRoot":"","sources":["../../../../src/cli/commands/fetch/all.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAOH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAwMpC,eAAO,MAAM,UAAU,SA2BnB,CAAC"}
+{"version":3,"file":"all.d.ts","sourceRoot":"","sources":["../../../../src/cli/commands/fetch/all.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAOH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AA8LpC,eAAO,MAAM,UAAU,SA2BnB,CAAC"}

package/dist/cli/commands/fetch/all.js

@@ -10,7 +10,7 @@ import { isManagerMode } from '../../../core/workspace/resolver.js';
 import chalk from 'chalk';
 import { Command } from 'commander';
 import { resolveCacheBehavior } from './fetch.utils.js';
-import { getReportById, resolveReportIds, resolveReportOutputDir, } from './fetch-manager.utils.js';
+import { buildReportConfig, getReportById, loadManagerConfigForFetch, resolveReportIds, resolveReportOutputDir, } from './fetch-manager.utils.js';
 import { fetchGitHubPRs } from './github/github.utils.js';
 import { fetchJiraTickets } from './jira/jira.utils.js';
 /**
@@ -89,28 +89,16 @@ async function fetchAllICMode(options) {
 async function fetchAllManagerMode(options) {
     const reportIds = await resolveReportIds(options);
     console.log(chalk.blue(`\n📥 Fetching all data for ${reportIds.length} report(s)...\n`));
-    // Load config once outside loop (for efficiency)
-    const baseConfig = await loadConfig(options.config);
+    // Load manager config once outside loop (for efficiency)
+    const managerConfig = loadManagerConfigForFetch();
     for (let i = 0; i < reportIds.length; i++) {
         const reportId = reportIds[i];
         const report = getReportById(reportId);
         console.log(chalk.blue(`\n=== Fetching data for ${report.name} (${i + 1}/${reportIds.length}) ===\n`));
         try {
             const outputDir = resolveReportOutputDir(reportId);
-            // Override config with report's credentials
-            const reportConfig = {
-                ...baseConfig,
-                github: {
-                    ...baseConfig.github,
-                    username: report.github, // Use report's GitHub username
-                },
-                jira: baseConfig.jira
-                    ? {
-                        ...baseConfig.jira,
-                        email: report.email, // Use report's Jira email
-                    }
-                    : undefined,
-            };
+            // Build IC-compatible config from manager config + report
+            const reportConfig = buildReportConfig(managerConfig, report);
             // Determine cache behavior - prompt if data exists and --cache not specified
             const useCache = await resolveCacheBehavior({
                 outputDir,

package/dist/cli/commands/fetch/fetch-manager.utils.d.ts

@@ -1,7 +1,8 @@
 /**
  * Manager mode fetch utilities
  */
-import type { ReportConfig } from '../../../core/types/manager.js';
+import type { Config } from '../../../core/config/schema.js';
+import type { ManagerConfig, ReportConfig } from '../../../core/types/manager.js';
 /**
  * Resolve report ID(s) for fetch operation
  *
@@ -26,4 +27,22 @@ export declare function getReportById(reportId: string): ReportConfig;
  * @returns Absolute path to report's work-log directory
  */
 export declare function resolveReportOutputDir(reportId: string): string;
+/**
+ * Load and return the manager config for the active profile.
+ *
+ * @returns Manager config validated against ManagerConfigSchema
+ */
+export declare function loadManagerConfigForFetch(): ManagerConfig;
+/**
+ * Build an IC-compatible Config from a manager config and a specific report.
+ *
+ * The fetch utilities (fetchGitHubPRs, fetchJiraTickets, linkPRsToTickets)
+ * all expect a Config (IC schema). This function bridges the gap by
+ * constructing one from the manager config + per-report overrides.
+ *
+ * @param managerConfig - The manager profile config
+ * @param report - The specific report to build the config for
+ * @returns A Config object compatible with IC fetch utilities
+ */
+export declare function buildReportConfig(managerConfig: ManagerConfig, report: ReportConfig): Config;
 //# sourceMappingURL=fetch-manager.utils.d.ts.map

package/dist/cli/commands/fetch/fetch-manager.utils.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"fetch-manager.utils.d.ts","sourceRoot":"","sources":["../../../../src/cli/commands/fetch/fetch-manager.utils.ts"],"names":[],"mappings":"AAAA;;GAEG;AAGH,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,mBAAmB,CAAC;AAOtD;;;;;GAKG;AACH,wBAAsB,gBAAgB,CAAC,OAAO,EAAE;IAC9C,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,UAAU,CAAC,EAAE,OAAO,CAAC;CACtB,GAAG,OAAO,CAAC,MAAM,EAAE,CAAC,CAyDpB;AAED;;;;;GAKG;AACH,wBAAgB,aAAa,CAAC,QAAQ,EAAE,MAAM,GAAG,YAAY,CAa5D;AAED;;;;;GAKG;AACH,wBAAgB,sBAAsB,CAAC,QAAQ,EAAE,MAAM,GAAG,MAAM,CAG/D"}
+{"version":3,"file":"fetch-manager.utils.d.ts","sourceRoot":"","sources":["../../../../src/cli/commands/fetch/fetch-manager.utils.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,gBAAgB,CAAC;AAE7C,OAAO,KAAK,EAAE,aAAa,EAAE,YAAY,EAAE,MAAM,mBAAmB,CAAC;AAOrE;;;;;GAKG;AACH,wBAAsB,gBAAgB,CAAC,OAAO,EAAE;IAC9C,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,UAAU,CAAC,EAAE,OAAO,CAAC;CACtB,GAAG,OAAO,CAAC,MAAM,EAAE,CAAC,CAyDpB;AAED;;;;;GAKG;AACH,wBAAgB,aAAa,CAAC,QAAQ,EAAE,MAAM,GAAG,YAAY,CAa5D;AAED;;;;;GAKG;AACH,wBAAgB,sBAAsB,CAAC,QAAQ,EAAE,MAAM,GAAG,MAAM,CAG/D;AAED;;;;GAIG;AACH,wBAAgB,yBAAyB,IAAI,aAAa,CAGzD;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,iBAAiB,CAC/B,aAAa,EAAE,aAAa,EAC5B,MAAM,EAAE,YAAY,GACnB,MAAM,CA+CR"}

package/dist/cli/commands/fetch/fetch-manager.utils.js

@@ -81,3 +81,68 @@ export function resolveReportOutputDir(reportId) {
     const activeProfile = getActiveProfile();
     return getReportWorkLogDir(activeProfile, reportId);
 }
+/**
+ * Load and return the manager config for the active profile.
+ *
+ * @returns Manager config validated against ManagerConfigSchema
+ */
+export function loadManagerConfigForFetch() {
+    const activeProfile = getActiveProfile();
+    return loadManagerConfig(activeProfile);
+}
+/**
+ * Build an IC-compatible Config from a manager config and a specific report.
+ *
+ * The fetch utilities (fetchGitHubPRs, fetchJiraTickets, linkPRsToTickets)
+ * all expect a Config (IC schema). This function bridges the gap by
+ * constructing one from the manager config + per-report overrides.
+ *
+ * @param managerConfig - The manager profile config
+ * @param report - The specific report to build the config for
+ * @returns A Config object compatible with IC fetch utilities
+ */
+export function buildReportConfig(managerConfig, report) {
+    // Build GitHub orgs array from manager org + report repos
+    const orgs = [
+        {
+            name: managerConfig.github.org,
+            repos: report.repos.length > 0 ? report.repos : ['*'],
+        },
+    ];
+    // Build JIRA instances from manager's JIRA config + report's projects
+    const jira = managerConfig.jira && report.jiraProjects.length > 0
+        ? {
+            instances: [
+                {
+                    name: managerConfig.jira.host,
+                    url: managerConfig.jira.host.startsWith('https://')
+                        ? managerConfig.jira.host
+                        : `https://${managerConfig.jira.host}`,
+                    email: report.email,
+                    token: managerConfig.jira.token,
+                    projects: report.jiraProjects,
+                },
+            ],
+        }
+        : undefined;
+    return {
+        github: {
+            username: report.github,
+            token: managerConfig.github.token,
+            orgs,
+        },
+        jira,
+        output: { directory: './work-log' },
+        fetch: {
+            since: managerConfig.fetch.since,
+            until: managerConfig.fetch.until,
+        },
+        analysis: {
+            thresholds: {
+                minor: { maxLines: 20, maxFiles: 3 },
+                major: { minLines: 200, minFiles: 8 },
+                flagship: { minLines: 500, minFiles: 15 },
+            },
+        },
+    };
+}

package/dist/cli/commands/fetch/github/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../../src/cli/commands/fetch/github/index.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAcH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAwHpC,eAAO,MAAM,aAAa,SA0BtB,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../../src/cli/commands/fetch/github/index.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAcH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAoHpC,eAAO,MAAM,aAAa,SA0BtB,CAAC"}

package/dist/cli/commands/fetch/github/index.js

@@ -11,7 +11,7 @@ import { getActiveProfile } from '../../../../core/workspace/global-config.js';
 import { isManagerMode } from '../../../../core/workspace/resolver.js';
 import chalk from 'chalk';
 import { Command } from 'commander';
-import { getReportById, resolveReportIds, resolveReportOutputDir, } from '../fetch-manager.utils.js';
+import { buildReportConfig, getReportById, loadManagerConfigForFetch, resolveReportIds, resolveReportOutputDir, } from '../fetch-manager.utils.js';
 import { fetchGitHubPRs } from './github.utils.js';
 /**
  * Fetch GitHub PRs in IC mode
@@ -43,22 +43,16 @@ async function fetchGitHubICMode(options) {
 async function fetchGitHubManagerMode(options) {
     const reportIds = await resolveReportIds(options);
     console.log(chalk.blue(`\n📥 Fetching GitHub PRs for ${reportIds.length} report(s)...\n`));
-    // Load base config
-    const baseConfig = await loadConfig(options.config);
+    // Load manager config
+    const managerConfig = loadManagerConfigForFetch();
     for (let i = 0; i < reportIds.length; i++) {
         const reportId = reportIds[i];
         const report = getReportById(reportId);
         console.log(chalk.blue(`\nFetching data for ${report.name} (${i + 1}/${reportIds.length})...`));
         try {
             const outputDir = resolveReportOutputDir(reportId);
-            // Override github.username with report's username
-            const reportConfig = {
-                ...baseConfig,
-                github: {
-                    ...baseConfig.github,
-                    username: report.github, // Use report's GitHub username, not manager's
-                },
-            };
+            // Build IC-compatible config from manager config + report
+            const reportConfig = buildReportConfig(managerConfig, report);
             // Determine cache behavior - prompt if data exists and --cache not specified
             let useCache = options.cache;
             if (!options.cache) {

package/dist/cli/commands/fetch/jira/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../../src/cli/commands/fetch/jira/index.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAcH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AA2HpC,eAAO,MAAM,WAAW,SA0BpB,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../../src/cli/commands/fetch/jira/index.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAcH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAqHpC,eAAO,MAAM,WAAW,SA0BpB,CAAC"}

package/dist/cli/commands/fetch/jira/index.js

@@ -11,7 +11,7 @@ import { getActiveProfile } from '../../../../core/workspace/global-config.js';
 import { isManagerMode } from '../../../../core/workspace/resolver.js';
 import chalk from 'chalk';
 import { Command } from 'commander';
-import { getReportById, resolveReportIds, resolveReportOutputDir, } from '../fetch-manager.utils.js';
+import { buildReportConfig, getReportById, loadManagerConfigForFetch, resolveReportIds, resolveReportOutputDir, } from '../fetch-manager.utils.js';
 import { fetchJiraTickets } from './jira.utils.js';
 /**
  * Fetch Jira tickets in IC mode
@@ -43,24 +43,16 @@ async function fetchJiraICMode(options) {
 async function fetchJiraManagerMode(options) {
     const reportIds = await resolveReportIds(options);
     console.log(chalk.blue(`\n📥 Fetching Jira tickets for ${reportIds.length} report(s)...\n`));
-    // Load base config (will be overridden per-report)
-    const baseConfig = await loadConfig(options.config);
+    // Load manager config
+    const managerConfig = loadManagerConfigForFetch();
     for (let i = 0; i < reportIds.length; i++) {
         const reportId = reportIds[i];
         const report = getReportById(reportId);
         console.log(chalk.blue(`\nFetching data for ${report.name} (${i + 1}/${reportIds.length})...`));
         try {
             const outputDir = resolveReportOutputDir(reportId);
-            // Override jira.email with report's email (if Jira is configured)
-            const reportConfig = {
-                ...baseConfig,
-                jira: baseConfig.jira
-                    ? {
-                        ...baseConfig.jira,
-                        email: report.email, // Use report's email, not manager's
-                    }
-                    : undefined,
-            };
+            // Build IC-compatible config from manager config + report
+            const reportConfig = buildReportConfig(managerConfig, report);
             // Determine cache behavior - prompt if data exists and --cache not specified
             let useCache = options.cache;
             if (!options.cache) {

package/dist/cli/commands/init/index.js

@@ -404,7 +404,9 @@ async function initManagerProfile(cliProfileName) {
         process.exit(1);
     }
     console.log(chalk.cyan('\nManager Mode Configuration\n'));
-    // Step 2: GitHub configuration
+    // Step 2: Time range
+    const { since, until } = await promptTimeRange();
+    // Step 3: GitHub configuration
     const githubOrg = await input({
         message: 'GitHub organization:',
         validate: (value) => {
@@ -415,7 +417,7 @@ async function initManagerProfile(cliProfileName) {
         },
     });
     const githubToken = await promptGitHubTokenForManager();
-    // Step 3: Optional JIRA configuration
+    // Step 4: Optional JIRA configuration
     const useJira = await confirm({
         message: 'Configure JIRA?',
         default: false,
@@ -462,16 +464,20 @@ async function initManagerProfile(cliProfileName) {
         tokens.jiraToken = jiraToken;
         tokens.jiraEmail = jiraEmail.trim();
     }
-    // Step 4: Create manager config
+    // Step 5: Create manager config
     const config = {
         mode: 'manager',
         github: {
             org: githubOrg.trim(),
         },
         jira: jiraConfig,
+        fetch: {
+            since,
+            until,
+        },
         reports: [],
     };
-    // Step 5: Create profile directories
+    // Step 6: Create profile directories
     ensureProfileDirs(profileName);
     // Save manager config as YAML
     const configPath = getProfileConfigPath(profileName);
@@ -485,7 +491,7 @@ async function initManagerProfile(cliProfileName) {
     // Set as active profile
     initializeWorkspaceWithProfile(profileName);
     console.log(chalk.green(`\nManager profile '${profileName}' created successfully!`));
-    // Step 6: Add reports?
+    // Step 7: Add reports?
     const addReportsNow = await confirm({
         message: 'Add reports now?',
         default: true,
@@ -516,7 +522,7 @@ async function initManagerProfile(cliProfileName) {
  */
 async function promptGitHubTokenForManager() {
     console.log(chalk.dim('\nCreate a token at: https://github.com/settings/tokens'));
-    console.log(chalk.dim('Required scopes: repo or public_repo\n'));
+    console.log(chalk.dim('Required scopes: repo or public_repo, read:org for orgs\n'));
     return await password({
         message: 'GitHub token:',
         validate: (value) => {

package/dist/cli/commands/init/init.prompts.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"init.prompts.d.ts","sourceRoot":"","sources":["../../../../src/cli/commands/init/init.prompts.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,cAAc,CAAC;AAEpD;;GAEG;AACH,MAAM,MAAM,UAAU,GAAG,QAAQ,GAAG,MAAM,CAAC;AAE3C;;GAEG;AACH,MAAM,MAAM,SAAS,GAAG,SAAS,GAAG,SAAS,GAAG,UAAU,GAAG,QAAQ,CAAC;AAEtE;;GAEG;AACH,MAAM,MAAM,mBAAmB,GAAG,QAAQ,GAAG,MAAM,GAAG,KAAK,CAAC;AAE5D;;GAEG;AACH,wBAAsB,iBAAiB,CACrC,WAAW,SAAY,GACtB,OAAO,CAAC,MAAM,CAAC,CAiBjB;AAED;;GAEG;AACH,wBAAsB,iBAAiB,IAAI,OAAO,CAAC,UAAU,EAAE,CAAC,CAgB/D;AAED;;GAEG;AACH,wBAAsB,eAAe,IAAI,OAAO,CAAC;IAC/C,KAAK,EAAE,MAAM,CAAC;IACd,KAAK,EAAE,MAAM,GAAG,IAAI,CAAC;IACrB,SAAS,EAAE,SAAS,CAAC;CACtB,CAAC,CAkED;AAcD;;GAEG;AACH,wBAAsB,oBAAoB,IAAI,OAAO,CAAC,MAAM,CAAC,CAU5D;AAED;;GAEG;AACH,wBAAsB,gBAAgB,IAAI,OAAO,CAAC,MAAM,EAAE,CAAC,CA8B1D;AAED;;GAEG;AACH,wBAAsB,yBAAyB,CAC7C,GAAG,EAAE,MAAM,GACV,OAAO,CAAC,mBAAmB,CAAC,CAyB9B;AAED;;GAEG;AACH,wBAAsB,qBAAqB,IAAI,OAAO,CAAC,eAAe,CAAC,CActE;AAED;;GAEG;AACH,wBAAsB,iBAAiB,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,EAAE,CAAC,CA4BtE;AAED;;GAEG;AACH,wBAAsB,4BAA4B,CAChD,KAAK,EAAE,MAAM,EAAE,GACd,OAAO,CAAC,KAAK,GAAG,IAAI,GAAG,MAAM,CAAC,CAiBhC;AAED;;GAEG;AACH,wBAAsB,eAAe,CAAC,KAAK,EAAE,MAAM,EAAE,GAAG,OAAO,CAAC,MAAM,EAAE,CAAC,CAKxE;AAED;;GAEG;AACH,wBAAsB,qBAAqB,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAC,OAAO,CAAC,CAWzE;AAED;;GAEG;AACH,wBAAsB,sBAAsB,IAAI,OAAO,CAAC,MAAM,CAAC,CAU9D;AAED;;GAEG;AACH,wBAAsB,aAAa,IAAI,OAAO,CAAC,MAAM,CAAC,CAqBrD;AAED;;GAEG;AACH,wBAAsB,eAAe,IAAI,OAAO,CAAC,MAAM,CAAC,CAavD;AAED;;GAEG;AACH,wBAAsB,kBAAkB,IAAI,OAAO,CAAC,MAAM,EAAE,CAAC,CA0B5D;AAED;;GAEG;AACH,wBAAsB,iBAAiB,CACrC,OAAO,EAAE,UAAU,EAAE,GACpB,OAAO,CAAC,OAAO,CAAC,CAuBlB;AAED;;GAEG;AACH,wBAAsB,iBAAiB,IAAI,OAAO,CAAC,MAAM,CAAC,CAUzD;AAED;;GAEG;AACH,wBAAsB,eAAe,IAAI,OAAO,CAAC,MAAM,CAAC,CAUvD;AAED;;GAEG;AACH,wBAAsB,cAAc,IAAI,OAAO,CAAC,OAAO,CAAC,CAKvD"}
+{"version":3,"file":"init.prompts.d.ts","sourceRoot":"","sources":["../../../../src/cli/commands/init/init.prompts.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,cAAc,CAAC;AAEpD;;GAEG;AACH,MAAM,MAAM,UAAU,GAAG,QAAQ,GAAG,MAAM,CAAC;AAE3C;;GAEG;AACH,MAAM,MAAM,SAAS,GAAG,SAAS,GAAG,SAAS,GAAG,UAAU,GAAG,QAAQ,CAAC;AAEtE;;GAEG;AACH,MAAM,MAAM,mBAAmB,GAAG,QAAQ,GAAG,MAAM,GAAG,KAAK,CAAC;AAE5D;;GAEG;AACH,wBAAsB,iBAAiB,CACrC,WAAW,SAAY,GACtB,OAAO,CAAC,MAAM,CAAC,CAiBjB;AAED;;GAEG;AACH,wBAAsB,iBAAiB,IAAI,OAAO,CAAC,UAAU,EAAE,CAAC,CAgB/D;AAED;;GAEG;AACH,wBAAsB,eAAe,IAAI,OAAO,CAAC;IAC/C,KAAK,EAAE,MAAM,CAAC;IACd,KAAK,EAAE,MAAM,GAAG,IAAI,CAAC;IACrB,SAAS,EAAE,SAAS,CAAC;CACtB,CAAC,CAkED;AAcD;;GAEG;AACH,wBAAsB,oBAAoB,IAAI,OAAO,CAAC,MAAM,CAAC,CAU5D;AAED;;GAEG;AACH,wBAAsB,gBAAgB,IAAI,OAAO,CAAC,MAAM,EAAE,CAAC,CA8B1D;AAED;;GAEG;AACH,wBAAsB,yBAAyB,CAC7C,GAAG,EAAE,MAAM,GACV,OAAO,CAAC,mBAAmB,CAAC,CAyB9B;AAED;;GAEG;AACH,wBAAsB,qBAAqB,IAAI,OAAO,CAAC,eAAe,CAAC,CActE;AAED;;GAEG;AACH,wBAAsB,iBAAiB,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,EAAE,CAAC,CA4BtE;AAED;;GAEG;AACH,wBAAsB,4BAA4B,CAChD,KAAK,EAAE,MAAM,EAAE,GACd,OAAO,CAAC,KAAK,GAAG,IAAI,GAAG,MAAM,CAAC,CAiBhC;AAED;;GAEG;AACH,wBAAsB,eAAe,CAAC,KAAK,EAAE,MAAM,EAAE,GAAG,OAAO,CAAC,MAAM,EAAE,CAAC,CAKxE;AAED;;GAEG;AACH,wBAAsB,qBAAqB,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAC,OAAO,CAAC,CAWzE;AAED;;GAEG;AACH,wBAAsB,sBAAsB,IAAI,OAAO,CAAC,MAAM,CAAC,CAU9D;AAED;;GAEG;AACH,wBAAsB,aAAa,IAAI,OAAO,CAAC,MAAM,CAAC,CAqBrD;AAED;;GAEG;AACH,wBAAsB,eAAe,IAAI,OAAO,CAAC,MAAM,CAAC,CAavD;AAED;;GAEG;AACH,wBAAsB,kBAAkB,IAAI,OAAO,CAAC,MAAM,EAAE,CAAC,CA0B5D;AAED;;GAEG;AACH,wBAAsB,iBAAiB,CACrC,OAAO,EAAE,UAAU,EAAE,GACpB,OAAO,CAAC,OAAO,CAAC,CA2BlB;AAED;;GAEG;AACH,wBAAsB,iBAAiB,IAAI,OAAO,CAAC,MAAM,CAAC,CAUzD;AAED;;GAEG;AACH,wBAAsB,eAAe,IAAI,OAAO,CAAC,MAAM,CAAC,CAUvD;AAED;;GAEG;AACH,wBAAsB,cAAc,IAAI,OAAO,CAAC,OAAO,CAAC,CAKvD"}

package/dist/cli/commands/init/init.prompts.js

@@ -172,7 +172,7 @@ export async function promptRepoDiscoveryMethod(org) {
             {
                 name: 'Auto-discover',
                 value: 'auto',
-                description: 'Find repos where you have PRs (slow for large orgs, may miss old contributions)',
+                description: 'Find repos where you have PRs (requires read:org scope for orgs, slow for large orgs)',
             },
             {
                 name: 'All repos (slowest)',
@@ -357,7 +357,7 @@ export async function promptTokensReady(sources) {
     console.log('Create your tokens at:');
     if (sources.includes('github')) {
         console.log(chalk.dim('  GitHub: https://github.com/settings/tokens'));
-        console.log(chalk.dim('          (Required scopes: repo or public_repo)'));
+        console.log(chalk.dim('          (Required scopes: repo or public_repo, read:org for orgs)'));
     }
     if (sources.includes('jira')) {
         console.log(chalk.dim('  JIRA:   https://id.atlassian.com/manage-profile/security/api-tokens'));

package/dist/cli/commands/init/init.utils.js

@@ -173,7 +173,16 @@ async function checkIfOrganization(graphqlWithAuth, login) {
         });
         return response.organization !== null;
     }
-    catch {
+    catch (error) {
+        // Check if this is an INSUFFICIENT_SCOPES error for read:org
+        if (error && typeof error === 'object' && 'errors' in error) {
+            const errors = error.errors;
+            if (errors?.some((e) => e.type === 'INSUFFICIENT_SCOPES')) {
+                throw new Error(`GitHub token is missing the 'read:org' scope, which is required to query organizations.\n` +
+                    `Please add this scope at: https://github.com/settings/tokens`);
+            }
+        }
+        // For other errors, assume it's a user (not an org)
         return false;
     }
 }

package/dist/core/types/manager.d.ts

@@ -30,6 +30,19 @@ export declare const ReportConfigSchema: z.ZodObject<{
     jiraProjects?: string[] | undefined;
 }>;
 export type ReportConfig = z.infer<typeof ReportConfigSchema>;
+/**
+ * Manager fetch configuration schema
+ */
+export declare const ManagerFetchConfigSchema: z.ZodObject<{
+    since: z.ZodString;
+    until: z.ZodDefault<z.ZodNullable<z.ZodString>>;
+}, "strip", z.ZodTypeAny, {
+    since: string;
+    until: string | null;
+}, {
+    since: string;
+    until?: string | null | undefined;
+}>;
 /**
  * Manager profile configuration schema
  */
@@ -58,6 +71,16 @@ export declare const ManagerConfigSchema: z.ZodObject<{
         host: string;
         token?: string | undefined;
     }>>;
+    fetch: z.ZodObject<{
+        since: z.ZodString;
+        until: z.ZodDefault<z.ZodNullable<z.ZodString>>;
+    }, "strip", z.ZodTypeAny, {
+        since: string;
+        until: string | null;
+    }, {
+        since: string;
+        until?: string | null | undefined;
+    }>;
     reports: z.ZodDefault<z.ZodArray<z.ZodObject<{
         /** Display name (e.g., "Alice Smith") */
         name: z.ZodString;
@@ -94,6 +117,10 @@ export declare const ManagerConfigSchema: z.ZodObject<{
         org: string;
         token?: string | undefined;
     };
+    fetch: {
+        since: string;
+        until: string | null;
+    };
     mode: "manager";
     jira?: {
         email: string;
@@ -105,6 +132,10 @@ export declare const ManagerConfigSchema: z.ZodObject<{
         org: string;
         token?: string | undefined;
     };
+    fetch: {
+        since: string;
+        until?: string | null | undefined;
+    };
     mode: "manager";
     reports?: {
         name: string;

package/dist/core/types/manager.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"manager.d.ts","sourceRoot":"","sources":["../../../src/core/types/manager.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;GAEG;AAEH;;GAEG;AACH,eAAO,MAAM,kBAAkB;IAC7B,yCAAyC;;IAEzC,sBAAsB;;IAEtB,wCAAwC;;IAExC,qCAAqC;;IAErC,6BAA6B;;;;;;;;;;;;;;EAE7B,CAAC;AACH,MAAM,MAAM,YAAY,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,kBAAkB,CAAC,CAAC;AAE9D;;GAEG;AACH,eAAO,MAAM,mBAAmB;;;;;;;;;;;;;;;;;;;;;;;;;;QAhB9B,yCAAyC;;QAEzC,sBAAsB;;QAEtB,wCAAwC;;QAExC,qCAAqC;;QAErC,6BAA6B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAsB7B,CAAC;AACH,MAAM,MAAM,aAAa,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,mBAAmB,CAAC,CAAC;AAEhE;;GAEG;AACH,MAAM,WAAW,cAAc;IAC7B,gCAAgC;IAChC,EAAE,EAAE,MAAM,CAAC;IACX,mBAAmB;IACnB,IAAI,EAAE,MAAM,CAAC;IACb,sBAAsB;IACtB,MAAM,EAAE,MAAM,CAAC;IACf,oBAAoB;IACpB,KAAK,EAAE,MAAM,CAAC;IACd,iCAAiC;IACjC,SAAS,EAAE,MAAM,CAAC;IAClB,yCAAyC;IACzC,gBAAgB,EAAE,MAAM,CAAC;IACzB,sCAAsC;IACtC,aAAa,CAAC,EAAE,MAAM,CAAC;CACxB"}
+{"version":3,"file":"manager.d.ts","sourceRoot":"","sources":["../../../src/core/types/manager.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;GAEG;AAEH;;GAEG;AACH,eAAO,MAAM,kBAAkB;IAC7B,yCAAyC;;IAEzC,sBAAsB;;IAEtB,wCAAwC;;IAExC,qCAAqC;;IAErC,6BAA6B;;;;;;;;;;;;;;EAE7B,CAAC;AACH,MAAM,MAAM,YAAY,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,kBAAkB,CAAC,CAAC;AAE9D;;GAEG;AACH,eAAO,MAAM,wBAAwB;;;;;;;;;EAGnC,CAAC;AAEH;;GAEG;AACH,eAAO,MAAM,mBAAmB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;QAxB9B,yCAAyC;;QAEzC,sBAAsB;;QAEtB,wCAAwC;;QAExC,qCAAqC;;QAErC,6BAA6B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA+B7B,CAAC;AACH,MAAM,MAAM,aAAa,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,mBAAmB,CAAC,CAAC;AAEhE;;GAEG;AACH,MAAM,WAAW,cAAc;IAC7B,gCAAgC;IAChC,EAAE,EAAE,MAAM,CAAC;IACX,mBAAmB;IACnB,IAAI,EAAE,MAAM,CAAC;IACb,sBAAsB;IACtB,MAAM,EAAE,MAAM,CAAC;IACf,oBAAoB;IACpB,KAAK,EAAE,MAAM,CAAC;IACd,iCAAiC;IACjC,SAAS,EAAE,MAAM,CAAC;IAClB,yCAAyC;IACzC,gBAAgB,EAAE,MAAM,CAAC;IACzB,sCAAsC;IACtC,aAAa,CAAC,EAAE,MAAM,CAAC;CACxB"}

package/dist/core/types/manager.js

@@ -17,6 +17,13 @@ export const ReportConfigSchema = z.object({
     /** Jira projects to fetch */
     jiraProjects: z.array(z.string()).default([]),
 });
+/**
+ * Manager fetch configuration schema
+ */
+export const ManagerFetchConfigSchema = z.object({
+    since: z.string(),
+    until: z.string().nullable().default(null),
+});
 /**
  * Manager profile configuration schema
  */
@@ -33,5 +40,6 @@ export const ManagerConfigSchema = z.object({
         token: z.string().optional(), // Token stored in .env, not config
     })
         .optional(),
+    fetch: ManagerFetchConfigSchema,
     reports: z.array(ReportConfigSchema).default([]),
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "work-chronicler",
-  "version": "0.2.2",
+  "version": "0.3.1",
   "description": "Gather, analyze, and summarize your work history from GitHub PRs and JIRA tickets for performance reviews and resumes",
   "type": "module",
   "main": "dist/cli/index.js",