angular-schule
diff --git a/‎.claude/ROADMAP.md‎
Lines changed: 589 additions & 0 deletions b/‎.claude/ROADMAP.md‎
Lines changed: 589 additions & 0 deletions
diff --git a/‎.claude/commands/document-end.md‎
Lines changed: 61 additions & 0 deletions b/‎.claude/commands/document-end.md‎
Lines changed: 61 additions & 0 deletions
diff --git a/‎.claude/commands/document-start.md‎
Lines changed: 69 additions & 0 deletions b/‎.claude/commands/document-start.md‎
Lines changed: 69 additions & 0 deletions
diff --git a/‎.claude/commands/git-quick.md‎
Lines changed: 95 additions & 0 deletions b/‎.claude/commands/git-quick.md‎
Lines changed: 95 additions & 0 deletions
diff --git a/‎.claude/commands/git-quick.sh‎
Lines changed: 71 additions & 0 deletions b/‎.claude/commands/git-quick.sh‎
Lines changed: 71 additions & 0 deletions
diff --git a/‎.github/workflows/test.yml‎
Lines changed: 52 additions & 0 deletions b/‎.github/workflows/test.yml‎
Lines changed: 52 additions & 0 deletions
diff --git a/‎.gitignore‎
Lines changed: 11 additions & 1 deletion b/‎.gitignore‎
Lines changed: 11 additions & 1 deletion
diff --git a/‎.gitmodules‎
Lines changed: 4 additions & 0 deletions b/‎.gitmodules‎
Lines changed: 4 additions & 0 deletions
diff --git a/‎.vscode-test.mjs‎
Lines changed: 15 additions & 0 deletions b/‎.vscode-test.mjs‎
Lines changed: 15 additions & 0 deletions
@@ -0,0 +1,61 @@
+---
+description: Preserve session context before auto-compact
+---
+
+# Session Context Preservation
+
+Please create a comprehensive session summary in `CLAUDE_TODO.md` that captures:
+
+## 1. Current Work Status
+- **Completed Tasks**: List all major changes made in this session
+- **In-Progress Tasks**: Any work that was started but not completed
+- **Blocked Items**: Any issues or questions that need resolution
+
+## 2. Technical Context
+- **Files Modified**: List all files that were changed with brief description of changes
+- **Files Created**: List any new files created (mark temporary investigation files clearly)
+- **Temporary/Debug Files**: If you created files like `DEBUG_*.md`, `INVESTIGATION_*.md` for debugging, mark them explicitly as "TEMPORARY - can be deleted after issue resolved"
+
+## 3. Important Decisions
+- **Architecture Choices**: Any significant technical decisions made
+- **Open Questions**: Unresolved technical or business logic questions
+
+## 4. Next Steps
+- **Immediate TODO**: What should be done first when resuming
+- **Testing Needed**: What needs to be tested or verified
+- **Documentation Updates**: Any *.md or other docs that need updating
+
+Format this as a structured markdown document that can be easily parsed when resuming work.
+
+If the file already exists and has content it means that we want to persist multiple continued sessions.
+Append your current session summary to the existing document, do NOT update existing content in the file.
+We want to tell the full story.
+
+## 5. How to Append Your Session Summary to the CLAUDE_TODO.md file
+
+**CRITICAL: Always use git root to locate the file correctly!**
+
+**Use Bash to append without reading the entire file:**
+
+Use the Bash tool with `>>` redirect to append your session summary directly to `CLAUDE_TODO.md` without needing to read the existing content first.
+
+**ALWAYS use this pattern to locate the file:**
+```bash
+cat >> "$(git rev-parse --show-toplevel)/CLAUDE_TODO.md" << 'EOF'
+
+---
+
+## Session: 2025-10-10 - Your Session Title
+
+Your session summary content here...
+
+EOF
+```
+
+This ensures the file is ALWAYS written to the correct location (git root), regardless of your current working directory. This allows efficient appending to arbitrarily large files without token concerns.
+
+## 6. Commit All Changes
+
+**If the session documentation was successful**, execute `/git-quick` to commit ALL open changes together with the updated `CLAUDE_TODO.md` file.
+
+Only do this if everything worked flawlessly during the session - if there were any errors or issues, skip this step and report the problem to the user. 
@@ -0,0 +1,69 @@
+---
+description: Resume work from previous session
+---
+
+# Resume Previous Session
+
+Please help me continue where we left off. Follow these steps:
+
+## 1. Load Previous Context - READ EVERYTHING INTO CONTEXT!
+
+**ABSOLUTE RULE: You MUST read the COMPLETE content of `CLAUDE_TODO.md` directly into your context. NO EXCEPTIONS.**
+
+### Step-by-Step Process (EXECUTE EXACTLY - NO DEVIATIONS):
+
+**STEP 0 - Locate Git Root (ALWAYS FIRST)**:
+
+Run `git rev-parse --show-toplevel` to find the project root directory. The `CLAUDE_TODO.md` file is ALWAYS at `$(git rev-parse --show-toplevel)/CLAUDE_TODO.md`.
+
+**STEP 1 - Count Total Lines (MANDATORY SECOND STEP)**:
+
+Run `wc -l $(git rev-parse --show-toplevel)/CLAUDE_TODO.md` to determine the file size.
+
+**STEP 2 - Calculate Chunks Needed**:
+- Chunk size: 2000 lines per chunk
+- Calculate: `chunks_needed = ceiling(total_lines / 2000)`
+- Example: 2897 lines → 2 chunks (lines 1-2000, then 2001-2897)
+
+**STEP 3 - Read ALL Chunks Sequentially**:
+
+⚠️ **YOU MUST read the file in chunks using offset/limit parameters.**
+
+**Do NOT attempt to read the entire file without offset/limit - it will fail for large files.**
+
+Read each chunk sequentially until you've loaded the entire file:
+
+**Example for 2897 lines (2 chunks):**
+- First message: Read with offset=1, limit=2000 (loads lines 1-2000)
+- Second message: Read with offset=2001, limit=897 (loads lines 2001-2897)
+
+**Example for 5500 lines (3 chunks):**
+- First message: Read with offset=1, limit=2000 (loads lines 1-2000)
+- Second message: Read with offset=2001, limit=2000 (loads lines 2001-4000)
+- Third message: Read with offset=4001, limit=1500 (loads lines 4001-5500)
+
+**Continue reading until ALL lines are loaded into context.**
+
+### What to Extract:
+From the complete session history in `CLAUDE_TODO.md`:
+- What story we were working on
+- What was completed
+- What remains to be done
+- Any blockers or open questions
+- All context needed to resume work
+
+## 2. Resume Work Plan
+Based on the TODO file:
+- Identify the next immediate task
+- Check for any dependencies or prerequisites
+- Determine if any context needs refreshing
+
+## 3. Provide Summary
+After reviewing, provide a brief summary:
+- Current story and progress
+- Next steps to take
+- Any issues that need addressing
+
+Then ask: "Should I continue with the next task?"
+
+Note: If `CLAUDE_TODO.md` doesn't exist or is empty, ask me what I'd like to work on today.
@@ -0,0 +1,95 @@
+---
+description: Quick commit and push with safety checks
+allowed-tools: Bash
+---
+
+# ⚠️ CRITICAL: TOKEN-SAVING INSTRUCTIONS FOR CLAUDE ⚠️
+
+**DO NOT** run any git commands before executing this script!
+**DO NOT** check git status, git diff, or any other commands!
+**DO NOT** analyze or inspect files!
+
+**ONLY DO THIS:**
+1. Craft a good commit message based on what was discussed
+2. DIRECTLY EXECUTE the script using the Bash tool with that message (DO NOT print or show the command)
+3. Let the script handle EVERYTHING else
+
+The script automatically handles:
+- Staging all changes
+- Creating the commit
+- Pulling latest changes
+- Pushing to origin
+- All safety checks
+
+**WASTING TOKENS ON PRELIMINARY CHECKS DEFEATS THE PURPOSE OF THIS AUTOMATION!**
+
+---
+
+Execute the automated git-quick script:
+
+```bash
+cd $(git rev-parse --show-toplevel) && ./.claude/commands/git-quick.sh "Your commit message here"
+```
+
+**IMPORTANT:** The assistant must use the Bash tool to execute this command directly, not display it.
+
+## Commit Message Guidelines
+
+Write comprehensive, multi-line commit messages that tell a complete story about the change. A great commit message should:
+
+### Structure:
+1. **Subject Line (First Line)**: 
+   - Start with conventional commit type: `feat:`, `fix:`, `chore:`, `docs:`, `refactor:`, `test:`, `style:`, `perf:`
+   - Keep under 72 characters
+   - Use imperative mood ("add feature" not "added feature")
+   - Capitalize first word after prefix
+   
+2. **Blank Line**: Always separate subject from body
+
+3. **Body (Detailed Explanation)**:
+   - Explain WHAT changed and WHY (not just how)
+   - Wrap lines at 72 characters for readability
+   - Use bullet points for multiple changes
+   - Include context about the problem being solved
+   - Mention any breaking changes or migrations needed
+   - Reference related issues or tickets
+
+4. **Footer (Optional)**:
+   - Breaking changes: `BREAKING CHANGE: description`
+   - Issue references: `Fixes #123`, `Closes #456`
+   - **NEVER add Co-authored-by for AI assistants or Claude**
+
+### Example of an Excellent Commit Message:
+
+```
+feat: Add multi-school support with active school selection
+
+Implements a global school selection system that allows users with access
+to multiple schools to switch between them seamlessly. The active school
+context is maintained throughout the application and persists across
+browser sessions.
+
+Key changes:
+- Added activeSchoolId signal to AuthService for reactive school tracking
+- Implemented setActiveSchool() method with automatic dashboard redirect
+- Created school selector dropdown component in the main navigation
+- Updated all API endpoints to accept schoolId parameter
+- Added localStorage persistence for selected school preference
+- Implemented validation to ensure selected school still exists on startup
+
+The system automatically selects the first non-personal school on login,
+falling back to the first available school if no institutional schools
+exist. This provides a smooth onboarding experience while maintaining
+flexibility for multi-school educators.
+
+Technical considerations:
+- School ID is passed as explicit parameter to maintain clean API contracts
+- No interceptors or hidden headers to avoid magic behavior
+- Reactive signals ensure UI updates automatically on school change
+- Cross-tab synchronization via localStorage events
+
+This change prepares the foundation for role-based features where teachers
+may have different permissions across different schools.
+
+Fixes #234
+BREAKING CHANGE: API endpoints now require explicit schoolId parameter
@@ -0,0 +1,71 @@
+#!/bin/bash
+
+# Git Quick Commit Script - Automates commit and push with safety checks
+# Usage: ./scripts/git-quick.sh "Your commit message here"
+
+set -e  # Exit on any error
+
+# Color codes for output
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+BLUE='\033[0;34m'
+NC='\033[0m' # No Color
+
+# Check if commit message was provided
+if [ -z "$1" ]; then
+    echo -e "${RED}Error: Please provide a commit message${NC}"
+    echo "Usage: $0 \"Your commit message here\""
+    exit 1
+fi
+
+COMMIT_MESSAGE="$1"
+
+echo -e "${BLUE}Starting git quick commit process...${NC}"
+
+# Step 1: Check current branch
+CURRENT_BRANCH=$(git branch --show-current)
+echo -e "${BLUE}Current branch: ${YELLOW}$CURRENT_BRANCH${NC}"
+
+if [[ "$CURRENT_BRANCH" == "stage-test" ]] || [[ "$CURRENT_BRANCH" == "stage-prod" ]]; then
+    echo -e "${RED}Error: Cannot commit directly to $CURRENT_BRANCH branch!${NC}"
+    echo -e "${RED}These branches are not intended for normal development.${NC}"
+    exit 1
+fi
+
+# Step 2: Stage all files
+echo -e "${BLUE}Staging all changes...${NC}"
+git add -A
+git status --short
+
+# Check if there are changes to commit
+if [ -z "$(git status --porcelain)" ]; then
+    echo -e "${YELLOW}No changes to commit${NC}"
+    exit 0
+fi
+
+# Step 3: Create commit
+echo -e "${BLUE}Creating commit...${NC}"
+git commit -m "$COMMIT_MESSAGE"
+COMMIT_SHA=$(git rev-parse HEAD)
+echo -e "${GREEN}Commit created: ${YELLOW}$COMMIT_SHA${NC}"
+
+# Step 4: Pull latest changes with rebase
+echo -e "${BLUE}Pulling latest changes with rebase...${NC}"
+if ! git pull --rebase origin "$CURRENT_BRANCH" 2>&1; then
+    echo -e "${RED}Rebase failed! Aborting rebase...${NC}"
+    git rebase --abort 2>/dev/null || true
+    echo -e "${RED}Please resolve conflicts manually and try again${NC}"
+    exit 1
+fi
+
+# Step 5: Push to origin
+echo -e "${BLUE}Pushing to origin...${NC}"
+git push origin "$CURRENT_BRANCH"
+
+# Step 6: Show final status
+echo -e "${GREEN}✓ Successfully pushed to origin/$CURRENT_BRANCH${NC}"
+echo -e "${BLUE}Final status:${NC}"
+git status --short --branch
+
+echo -e "${GREEN}Commit ${YELLOW}$COMMIT_SHA${GREEN} has been successfully pushed!${NC}"
@@ -0,0 +1,52 @@
+name: Test Mini TypeScript Hero
+
+on:
+  push:
+    branches: [main, mini-typescript-hero-v4]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    name: Test on ${{ matrix.os }}
+    timeout-minutes: 10  # Tests take ~2-3min, add buffer for CI overhead
+    strategy:
+      matrix:
+        os: [macos-latest, ubuntu-latest, windows-latest]
+    runs-on: ${{ matrix.os }}
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          submodules: true  # Checkout submodule at pinned commit from repo
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '18.x'
+
+      - name: Install main dependencies
+        run: npm install
+
+      - name: Run main extension tests (Linux with xvfb)
+        if: runner.os == 'Linux'
+        run: xvfb-run -a npm test
+
+      - name: Run main extension tests (macOS/Windows)
+        if: runner.os != 'Linux'
+        run: npm test
+
+      - name: Install comparison tests dependencies
+        run: npm install
+        working-directory: ./tests/comparison
+
+      - name: Run comparison tests (Linux with xvfb)
+        if: runner.os == 'Linux'
+        run: xvfb-run -a npm test
+        working-directory: ./tests/comparison
+
+      - name: Run comparison tests (macOS/Windows)
+        if: runner.os != 'Linux'
+        run: npm test
+        working-directory: ./tests/comparison
@@ -1,10 +1,20 @@
 out
+dist
 node_modules
 .vscode-test
 *.vsix
 
+# NOTE: dist/ is ignored in git but INCLUDED in VSIX via .vscodeignore
+# Build artifacts should not be committed to version control
+# CI/CD or local build generates dist/ before packaging
+
+# Test workspace contents (keep structure, ignore generated files)
+tests/workspaces/**/mths-workspace-*
+
 # Logs
 logs
 *.log
 npm-debug.log*
-coverage/
+coverage/
+.DS_Store
+.claude/settings.local.json
@@ -0,0 +1,4 @@
+[submodule "tests/comparison/old-typescript-hero"]
+	path = tests/comparison/old-typescript-hero
+	url = https://github.com/angular-schule/mini-typescript-hero.git
+	branch = old-ts-hero-v3
@@ -0,0 +1,15 @@
+import { defineConfig } from '@vscode/test-cli';
+import path from 'path';
+import { fileURLToPath } from 'url';
+
+const __dirname = path.dirname(fileURLToPath(import.meta.url));
+
+export default defineConfig({
+	files: 'out/tests/unit/**/*.test.js',
+	workspaceFolder: path.join(__dirname, 'tests/workspaces/single-root'),
+	// Use short path to avoid macOS socket path length limit (103 chars)
+	launchArgs: ['--user-data-dir=/tmp/mths-user-data'],
+	mocha: {
+		timeout: 10000 // Increased from default 2000ms for slower CI environments (especially macOS)
+	}
+});