refactor: Update copilot instructions for clarity and structure

Author: MatFillion

.github/copilot-instructions.md

@@ -1,54 +1,41 @@
+````instructions
 ```language: .vscode-copilot-instructions
 
-You are a software engineer working on a VS Code extension called "Prompts Sync Extension" that synchronizes GitHub Copilot prompts from Git repositories. Key points about the codebase:
+You are a software engineer working on a VS Code extension named "Promptitude" that syncs GitHub Copilot prompts from Git repositories to the local VS Code prompts folder.
+**Always** ask for clarification and present your plan and reasoning before modifying code.
+Update the instructions below as the codebase evolves.
+Update the CHANGELOG.md with each significant change.
+Warn me about backward-incompatible changes.
 
-1. Core Components:
-- Main extension entry: [src/extension.ts](src/extension.ts) handles activation and command registration
-- Sync management: [src/syncManager.ts](src/syncManager.ts) orchestrates the sync process
-- Config handling: [src/configManager.ts](src/configManager.ts) manages extension settings
-- Status bar: [src/statusBarManager.ts](src/statusBarManager.ts) shows sync status
-- GitHub API: [src/utils/github.ts](src/utils/github.ts) handles repository operations
-- File operations: [src/utils/fileSystem.ts](src/utils/fileSystem.ts) manages local file system
+Architecture & key files
+- Entry/activation: src/extension.ts – activates on startup, wires ConfigManager, StatusBarManager, SyncManager; registers commands:
+  promptitude.syncNow • promptitude.showStatus • promptitude.openPromptsFolder • promptitude.addAzureDevOpsPAT • promptitude.clearAzureDevOpsPAT • promptitude.clearAzureDevOpsCache
+- Sync: src/syncManager.ts – schedules by promptitude.frequency; per-repo (url or url|branch, default main) select provider via GitProviderFactory, authenticate, fetch tree, filter, download files. Filters chatmode/, instructions/, prompts/ and .md/.txt; writes files flat to the prompts directory using the basename (last write wins).
+- Configuration: src/configManager.ts – reads promptitude.*; repositoryConfigs parses url|branch; getPromptsDirectory returns OS-specific path; flags: enabled, syncOnStartup, showNotifications, debug, syncChatmode, syncInstructions, syncPrompt.
+- Providers: src/utils/github.ts (VS Code GitHub auth with scope repo; REST branches→sha→git/trees; contents for files). src/utils/azureDevOps.ts (PATs in SecretStorage; per-organization PAT index cached in globalState; supports dev.azure.com and legacy visualstudio.com; owner encoded as organization|project|baseUrl).
+- Utilities/UI: src/utils/fileSystem.ts (fs ops); src/utils/notifications.ts (messages + auth flows); src/utils/logger.ts (single "Promptitude" output channel; debug gated by setting); src/statusBarManager.ts (Idle/Syncing/Success/Error + last sync time; click triggers sync).
 
-2. Key Features:
-- Multi-repository sync support with error handling
-- Configurable sync frequency (startup/hourly/daily/weekly/manual)
-- Cross-platform file path handling
-- GitHub authentication via VS Code's built-in auth
-- Status bar integration with sync indicators
-- Selective sync for different prompt types (chatmode/instructions/prompt)
+Developer workflows
+- Build/package: npm install → npm run compile (or npm run watch) → npm run package (VSIX). Lint: npm run lint. Tests: npm run test.
+- Debug: set "promptitude.debug": true; read logs in Output → Promptitude; use Command Palette to run the commands above. Extension activates onStartupFinished.
 
-3. Best Practices:
-- Use TypeScript with strict type checking
-- Follow VS Code extension guidelines
-- Implement proper error handling and logging
-- Use async/await for asynchronous operations
-- Support cross-platform paths
-- Provide clear user feedback through notifications
-- Maintain backward compatibility
-- Handle GitHub API rate limits
+Conventions & patterns (repo-specific)
+- No console.log. Use Logger.get('Scope').debug|info|warn|error (debug visible only when promptitude.debug = true).
+- Always use FileSystemManager for IO and NotificationManager for UX/auth prompts; do not duplicate provider auth logic.
+- Settings drive behavior; avoid hard-coded paths/branches; use ConfigManager.repositoryConfigs for url|branch parsing.
+- Provider code lives in GitApiManager implementations; select via GitProviderFactory.createFromUrl().
+- Duplicate filenames across repos overwrite by last processed repo (flat output). Allowed file types: .md, .txt.
 
-4. Common Tasks:
-- File operations should use [FileSystemManager](src/utils/fileSystem.ts)
-- GitHub API calls through [GitHubApiManager](src/utils/github.ts)
-- Configuration changes via [ConfigManager](src/configManager.ts)
-- Status updates using [StatusBarManager](src/statusBarManager.ts)
-- Error logging through [Logger](src/utils/logger.ts)
-- User notifications via [NotificationManager](src/utils/notifications.ts)
-
-5. Repository Structure:
-- Source code in `src/` with TypeScript files
-- Configuration in `package.json`
-- Build settings in `tsconfig.json`
-- ESLint config in `.eslintrc.js`
-- GitHub workflows in `.github/workflows/`
-
-When suggesting code:
-- Use TypeScript with proper type annotations
-- Follow existing error handling patterns
-- Consider cross-platform compatibility
-- Include appropriate logging statements
-- Add JSDoc comments for public APIs
-- Handle VS Code disposal and cleanup
-- Consider backward compatibility
-```
+Examples
+- settings.json:
+  {
+    "promptitude.repositories": [
+      "https://github.com/org/prompts",
+      "https://github.com/org/prompts|develop",
+      "https://dev.azure.com/acme/Project/_git/prompt-repo|release"
+    ]
+  }
+- Logging:
+  const log = Logger.get('MyFeature'); log.info('Starting'); log.debug('Detailed trace when promptitude.debug = true');
+```
+````