Full Code of JocysCom/FocusLogger for AI

Repository: JocysCom/FocusLogger
Branch: main
Commit: bd497bb745a6
Files: 88
Total size: 826.0 KB

Directory structure:
gitextract_pkit4a3b/

├── .ai/
│   ├── ReadMe.md
│   ├── coding-guideline.instructions.md
│   ├── instructions.md
│   ├── repository-analysis.instructions.md
│   └── skills/
│       └── ai-self-improvement/
│           ├── SKILL.md
│           └── scripts/
│               └── Sync-AgentAssets.ps1
├── .claude/
│   ├── coding-guideline.instructions.md
│   ├── instructions.md
│   ├── repository-analysis.instructions.md
│   └── skills/
│       └── ai-self-improvement/
│           ├── SKILL.md
│           └── scripts/
│               └── Sync-AgentAssets.ps1
├── .editorconfig
├── .github/
│   ├── copilot-instructions.md
│   ├── instructions/
│   │   ├── coding-guideline.instructions.md
│   │   └── repository-analysis.instructions.md
│   └── skills/
│       └── ai-self-improvement/
│           ├── SKILL.md
│           └── scripts/
│               └── Sync-AgentAssets.ps1
├── .gitignore
├── .markdownlint.json
├── Documents/
│   ├── App_1_Sign.ps1
│   ├── App_2_Zip.ps1
│   ├── Take_Screenshot.ps1
│   └── Take_Screenshot.ps1.cs
├── FocusLogger/
│   ├── App.xaml
│   ├── App.xaml.cs
│   ├── AssemblyInfo.cs
│   ├── Common/
│   │   ├── DataItem.cs
│   │   ├── DataItemType.cs
│   │   └── NativeMethods.cs
│   ├── Controls/
│   │   ├── DataListControl.xaml
│   │   └── DataListControl.xaml.cs
│   ├── JocysCom/
│   │   ├── Collections/
│   │   │   └── CollectionsHelper.cs
│   │   ├── Common/
│   │   │   └── Helper.cs
│   │   ├── ComponentModel/
│   │   │   ├── BindingListInvoked.cs
│   │   │   ├── NotifyPropertyChanged.cs
│   │   │   ├── PropertyComparer.cs
│   │   │   └── SortableBindingList.cs
│   │   ├── Configuration/
│   │   │   ├── Arguments.cs
│   │   │   ├── AssemblyInfo.cs
│   │   │   ├── ISettingsData.cs
│   │   │   ├── ISettingsFileItem.cs
│   │   │   ├── ISettingsItem.cs
│   │   │   ├── ISettingsListFileItem.cs
│   │   │   ├── SettingsData.cs
│   │   │   ├── SettingsHelper.cs
│   │   │   ├── SettingsItem.cs
│   │   │   └── SettingsParser.cs
│   │   ├── Controls/
│   │   │   ├── ControlsHelper.WPF.UseWindowsForms.cs
│   │   │   ├── ControlsHelper.WPF.cs
│   │   │   ├── ControlsHelper.cs
│   │   │   ├── InfoControl.xaml
│   │   │   ├── InfoControl.xaml.cs
│   │   │   ├── InfoHelpProvider.cs
│   │   │   ├── InitHelper.cs
│   │   │   ├── ItemFormattingConverter.cs
│   │   │   ├── MessageBoxWindow.xaml
│   │   │   ├── MessageBoxWindow.xaml.cs
│   │   │   ├── TabIndexConverter.cs
│   │   │   ├── Themes/
│   │   │   │   ├── Convert_SVG_to_XAML.ps1
│   │   │   │   ├── Default.xaml
│   │   │   │   ├── Default_MultiReplace.ps1
│   │   │   │   ├── Icons.xaml
│   │   │   │   └── Icons.xaml.cs
│   │   │   └── ToolStripBorderlessRenderer.cs
│   │   ├── Data/
│   │   │   └── SqlHelper.Types.cs
│   │   ├── IO/
│   │   │   └── PathHelper.cs
│   │   ├── MakeLinks_Ref.ps1
│   │   ├── Runtime/
│   │   │   ├── RuntimeHelper.cs
│   │   │   └── Serializer.cs
│   │   └── Text/
│   │       └── Helper.cs
│   ├── JocysCom.FocusLogger.csproj
│   ├── MainWindow.xaml
│   ├── MainWindow.xaml.cs
│   └── Resources/
│       ├── AiAnalysisPrompt.md
│       └── Icons/
│           ├── Convert_SVG_to_XAML.ps1
│           ├── IconExperience.License.txt
│           ├── Icons_Default.xaml
│           └── Icons_Default.xaml.cs
├── FocusLogger.Tests/
│   ├── CsvExportTests.cs
│   ├── JocysCom.FocusLogger.Tests.csproj
│   └── UIAutomationTests.cs
├── JocysCom.FocusLogger.slnx
├── LICENSE
├── README.md
├── Resources/
│   └── ZipFiles.ps1
├── SECURITY.md
├── Settings.XamlStyler
└── Solution_Cleanup.ps1

================================================
FILE CONTENTS
================================================

================================================
FILE: .ai/ReadMe.md
================================================
## Files

- `developer-info.md` - Developer information about the solution, which will be used when creating the repository-analysis.instructions.md file.
- `instructions.md` - Main AI Agent System Message instructions used by AI Agents, like CLINE or CoPilot.
- `repository-analysis.instructions.md` - Autogenerated Repository Analysis file that is supplied to the AI Agent as a System message after instructions.md.
- `repository-analysis.prompt.md` - User Message prompt that instructs AI to create repository-analysis.instructions.md.
- `Update-AgentInstructions.ps1` - Sets all `*instruction.md` files as AI agent system message instruction files. Used by AI agents, like CLINE or Copilot.

## Custom instructions: GitHub Copilot

With GitHub Copilot, you can receive chat responses tailored to your team'ss workflow, preferred tools, and project specifics.
Instead of adding this contextual detail to each chat query, you can create a file that supplies this information automatically.
While this additional context won't appear in the chat, it is available to GitHub Copilot, allowing it to generate more accurate and relevant responses.

**How to Enable Custom Instructions**

Enable the feature via Tools > Options > GitHub > Copilot > and check (Preview) Enable custom instructions to be loaded from .github/copilot-instructions.md files and added to requests.
Add copilot-instruction.md in the root of your respository inside the .github file, create the file if it doesn't already exist.
GitHub Copilot Enable Custom Instructions

Learn more about creating custom instructions:
https://docs.github.com/en/enterprise-cloud@latest/copilot/customizing-copilot/adding-custom-instructions-for-github-copilot

## Custom instructions: CLINE

All CLINE instructions are stored inside the .clinerules\ folder.
All \*.md files will be loaded as system messages.

## Custom instructions: OpenAI Codex

Instructions are stored in `%USERPROFILE%\.codex\instructions.md` file.


## User Instructions to create `repository-analysis.md`

Note: Switch AI agent to `Plan` mode before submitting this message. This will yield better results.


### LLM Selection Guideline

If your deployment environment allows, prefer a newer, higher-capacity model—such as Anthropic Claude Sonnet 4 or Google Gemini 2.5 Pro - instead of the current OpenAI GPT 4 lineup.  These frontier models typically deliver stronger reasoning, broader context windows, and more consistent output quality on complex tasks.

### Install the Mermaid preview plug-in

	1. Open Extensions (Ctrl + Shift + X).
	2. Search: Markdown Preview Mermaid Support (publisher: Matt Bierner).
	3. Click Install – or hit Ctrl + P.
	
### Open Preview

	1. Open the menu on the tab header of the file.
	2. Click "Open Preview" – or hit Ctrl + Shift + V.
	
### Re Open Preview

	1. Open the menu on the tab header of the file.
	2. Click "Reopen Editor With..."
	3. Click "Markdown Preview (Built-In)"


================================================
FILE: .ai/coding-guideline.instructions.md
================================================
# Coding Guidelines

- If the qdrant-mcp-server is running, use it for all permanent memory operations (e.g. storing user information).
- After making changes, ALWAYS start a new server for testing.
- Kill all existing related servers from previous testing before starting a new server.
- Prefer the simplest viable solution; avoid over-engineering.
- Do not add broad try/catch or wrapper layers unless required by a failing test or explicit requirement; if you catch, rethrow to preserve the stack.
- Before writing new code, actively look for existing utilities or functions that can be reused instead of duplicated.
- New helper methods or classes must be justified with a clear, documented need for functionality that is unavailable elsewhere in the codebase.
- Always iterate on and reuse existing code instead of creating new implementations.
- Avoid adding layers of abstraction that do not deliver clear value.
- Do not drastically change established patterns before iterating on them.
- No duplication / SSOT: update or move existing code instead of adding parallel implementations. If you introduce a replacement, remove the old one **in the same change**.
- Write code that accounts for different environments (dev, test, and prod).
- Only modify what is explicitly requested or clearly necessary; do **not** create new files or modules unless explicitly requested.
- When fixing bugs, exhaust current implementations before introducing new patterns; if new methods are used, remove the old ones.
- Keep the codebase clean and organized.
- Avoid one-off scripts unless absolutely necessary.
- Use mocks only for tests, not for dev or prod.
- Never add stubbing or fake data in dev or prod environments.
- Never overwrite the .env file without explicit confirmation.
- Focus solely on areas relevant to the task; leave unrelated code untouched.
- Write thorough tests for all major functionality.
- Avoid major changes to the existing architecture unless explicitly instructed.
- Always consider the impact on other methods and areas of the code.
- Prefer to wrap long lines for better readability.
- Preserve existing formatting; limit formatting to lines you changed and match surrounding style. Also remove any unused imports/usings or dead code **introduced by your edits**.
- Stability primitives (repeatability > cleverness): when the repo provides an established way to perform an operation (repo-owned script, documented command snippet, standard PS1 under .ai/Scripts), treat it as the single source of truth. Use it verbatim instead of synthesizing “equivalent” commands. Only deviate when explicitly asked or when the primitive is proven broken in this environment (and then fix the primitive, not invent a parallel path).
- No code file that you **create or modify** may exceed **6000 tokens (~24 KB)** once your changes are applied.
  - If your changes alone would push the file past this limit, either trim the change or ask for explicit permission to refactor; do **not** alter unrelated code solely to meet the limit.
  - Existing oversized files are left untouched unless the user explicitly requests a refactor.

## Source Control Conventions

Naming conventions for issues, branches, and pull requests.

### Categories

| Category | Use for |
|----------|---------|
| `FEAT`   | New features |
| `FIX`    | Bug fixes |
| `TECH`   | Infrastructure, dependencies, refactoring |
| `DOCS`   | Documentation |

### Naming Patterns

| Item       | Pattern | Example |
|------------|---------|---------|
| **Issue**  | `{CATEGORY}: {Description}` | `FEAT: Download logs to CSV` |
| **Branch** | `{CATEGORY}-{issue#}-{lowercase-dashed-name}` | `FEAT-21-download-logs-to-csv` |
| **PR**     | `PR: #{issue#}: {CATEGORY}: {Description}` | `PR: #21: FEAT: Download logs to CSV` |

- Branch names: lowercase, words separated by dashes, non-ASCII replaced with a single dash, derived from issue title but may be shortened.
- PR body must reference the issue with `Closes #{issue#}`.
- Merge via PR only — no direct pushes to `main` or `master`.
- Feature branches are always created from `main` or `master`. Never merge one feature branch into another — only merge `main` if you need to catch up.
- Always create branches from latest origin/main or origin/main, never merge sub-branches, confirm before risky git ops.
- Do not add Co-Authored-By {AI model}/{AI company} lines to commits.
- Never close issues before a release is published with the fix.

Use the following guidelines:

1. Doc Comment Enhancement for IntelliSense

    - Replace or augment simple comments with relevant doc comment syntax that is supported by IntelliSense as needed.
    - Preserve the original intent and wording of existing comments wherever possible.

2. Code Layout for Clarity

    - Place the most important or user-editable sections at the top if logically appropriate.
    - Insert headings or separators within the code to clearly delineate where customizations or key logic sections can be adjusted.

3. No Extraneous Code Comments

    - Do not include "one-off" or user-directed commentary in the code.
    - Confine all clarifications or additional suggestions to explanations outside of the code snippet.

4. Avoid Outdated or Deprecated Methods

    - Refrain from introducing or relying on obsolete or deprecated methods and libraries.
    - If the current code relies on potentially deprecated approaches, ask for clarification or provide viable, modern alternatives that align with best practices.

5. Testing and Validation

    - Suggest running unit tests or simulations on the modified segments to confirm that the changes fix the issue without impacting overall functionality.
    - Ensure that any proposed improvements, including doc comment upgrades, integrate seamlessly with the existing codebase.
    - After all code modifications, navigate to the affected project directory and build C# then Angular to confirm the application compiles without errors:
		cd {PROJECT} && dotnet build {PROJECT}.csproj
		cd {PROJECT}/ClientApp && ng build
    - Run relevant unit tests if code changes affect core logic.
    - If the developer certificate is not trusted, then execute: dotnet dev-certs https --trust
    - To launch project use: dotnet watch run --project {PROJECT}/{PROJECT}.csproj --launch-profile "{PROJECT} (NG Build)"

6. Rationale and Explanation

    - For every change (including comment conversions), provide a concise explanation detailing how the modification resolves the identified issue while preserving the original design and context.
    - Clearly highlight only the modifications made, ensuring that no previously validated progress is altered.
    - NOTE: Summarize reasoning for the user, but do NOT expose full chain-of-thought. Keep internal deliberations internal; surface only the concise rationale needed to justify each change.

7. Contextual Analysis

    - Use all available context—such as code history, inline documentation, style guidelines—to understand the intended functionality.
    - When inspecting an existing file for understanding, prefer reading the whole file in a
      single `read_file` call when it comfortably fits in context; switch to targeted slices
      only when the file is too large, the tool truncates it, or a specific anchor line is
      already known.
    - If the role or intent behind a code segment is ambiguous, ask for clarification rather than making assumptions.

8. Targeted, Incremental Changes

    - Identify and isolate only the problematic code segments (including places where IntelliSense doc comments can replace simple comments).
    - Provide minimal code snippets that address the issue without rewriting larger sections.
    - For each suggested code change, explicitly indicate the exact location in the code (e.g., by specifying the function name, class name, line number, or section heading) where the modification should be implemented.

9. Preservation of Context

    - Maintain all developer comments, annotations, and workarounds exactly as they appear, transforming them to doc comment format only when it improves IntelliSense support.
    - Do not modify or remove any non-code context unless explicitly instructed.
    - Avoid introducing new, irrelevant comments in the code.

10. Launching {PROJECT} Correctly:
    - Navigate to the {PROJECT} project folder.
    - Run the following command to launch the project with live reload and proper debugging configuration:
      dotnet watch run --launch-profile "{PROJECT} (NG Build)" --project {PROJECT}/{PROJECT}.csproj
    - This command will start the {PROJECT} project on the designated debugging session URL.
    - Ensure that any previous {PROJECT} instances are terminated before running this command.


================================================
FILE: .ai/instructions.md
================================================
## Role

Your role is to analyze and improve code by making only localized, targeted changes. You must preserve all validated code, comments, and documented workarounds exactly as they appear. Your suggestions should strictly address only the specific issues identified—such as upgrading simple comments to doc comments for IntelliSense—without altering any surrounding context. Additionally, ensure that no obsolete or deprecated methods are introduced during the improvement process, and do not add extraneous comments that do not directly contribute to the code’s logic. Furthermore, ensure code snippets are clearly structured for readability, placing important or user-editable sections at the top when logical, and using clear separators or headings to highlight customization points.
Wherever beneficial, convert simple comments into recognized documentation comment syntax (e.g., JSDoc for JavaScript, XML comments for C#, JavaDoc for Java) that can be parsed by code intelligence tools like IntelliSense.
Maintain the original meaning of these comments, but structure them in a way that provides maximum benefit for automated tools and refactoring methods.
Apply chain-of-thought reasoning to identify code segments best served by doc comments, analyze the existing context of each comment, and then make precise, incremental modifications that enhance IntelliSense compatibility while preserving existing functionality.

## Output

Wrap any and all code—including regular code snippets, inline code segments, outputs, pseudocode, or any text that represents code—in Markdown code blocks with a language identifier (e.g., ```typescript, ```powershell).


================================================
FILE: .ai/repository-analysis.instructions.md
================================================
# Repository Analysis

## 1. Repository Overview

This document provides a factual reference for the Jocys.com FocusLogger repository, aimed at developers and AI coding agents working on the codebase.

**FocusLogger** is a Windows desktop utility that monitors and logs which process or program takes window focus. It targets users (especially gamers and power users) who experience unexpected focus stealing — where a background process briefly grabs foreground focus, interrupting gameplay or work. The tool logs every focus change with timestamps, process details, window class names, and focus-state flags, allowing users to identify the culprit.

- **Repository:** https://github.com/JocysCom/FocusLogger
- **License:** GNU General Public License v3.0
- **Current version:** 1.2.6
- **Target platform:** Windows 10+ with .NET 8.0
- **Primary audiences:** Gamers, power users, IT support personnel diagnosing focus-stealing issues.

## 2. Top-Level Structure

This section maps every top-level directory and file to help navigate the repository quickly.

| Path | Purpose |
|------|---------|
| `FocusLogger/` | Main application project (WPF, .NET 8.0). Contains all app source code, shared library, and resources. |
| `FocusLogger.Tests/` | MSTest test project. Unit tests for CSV export and UI automation tests. |
| `Documents/` | Release engineering: signing scripts, zip packaging scripts, screenshot tooling, and pre-built release files. |
| `Resources/` | Solution-level shared scripts (currently `ZipFiles.ps1` for checksum-aware zip packaging). |
| `.ai/` | AI agent instructions, coding guidelines, repository analysis, and skills. |
| `JocysCom.FocusLogger.slnx` | Solution file (XML-based `.slnx` format) referencing the two projects. |
| `README.md` | Project overview, download link, system requirements, screenshot. |
| `LICENSE` | GPLv3 license text. |
| `SECURITY.md` | Security vulnerability reporting policy (support@jocys.com). |
| `Settings.XamlStyler` | XamlStyler configuration for consistent XAML formatting. |
| `Solution_Cleanup.ps1` | PowerShell script for cleaning build artifacts. |

## 3. Technology Stack & Key Dependencies

This section lists verified technologies and versions drawn from project files.

| Technology | Version / Detail | Evidence |
|------------|-----------------|----------|
| .NET | 8.0 (`net8.0-windows`) | `JocysCom.FocusLogger.csproj` TargetFramework |
| C# | Implicit (SDK default for .NET 8) | SDK-style project |
| WPF | `<UseWPF>true</UseWPF>` | csproj |
| Windows Forms interop | `<UseWindowsForms>true</UseWindowsForms>` | csproj — used for P/Invoke helpers and DPI awareness |
| MSTest | v3.x (`MSTest.TestFramework 3.*`, `MSTest.TestAdapter 3.*`) | Test csproj PackageReference |
| Microsoft.NET.Test.Sdk | 17.x | Test csproj PackageReference |
| Windows API (user32.dll) | P/Invoke | `NativeMethods.cs` |
| PowerShell | Scripts for build, sign, zip, cleanup | `Documents/`, `Resources/`, root |
| XamlStyler | Config present | `Settings.XamlStyler` |

**No NuGet package dependencies** in the main application project — all functionality comes from .NET SDK and the embedded `JocysCom.ClassLibrary`.

## 4. Architecture & Runtime Model

This section describes how the application is structured and how it operates at runtime.

FocusLogger is a **single-executable WPF desktop application** that polls Windows API functions to detect focus changes. It does not persist log data between sessions (in-memory only) but provides CSV export for offline analysis.

### Architectural layers

```mermaid
graph TD
    subgraph UI["UI Layer (WPF)"]
        App["App.xaml.cs<br/>Entry point, DPI aware"]
        MW["MainWindow.xaml.cs<br/>Main window frame"]
        DLC["DataListControl.xaml.cs<br/>Core logging UI + logic"]
    end

    subgraph Core["Core Logic"]
        DI["DataItem.cs<br/>Log entry model"]
        DIT["DataItemType.cs<br/>Entry type enum"]
        NM["NativeMethods.cs<br/>P/Invoke declarations"]
        CSV["CSV Export<br/>BuildCsvContent, CsvEscape"]
    end

    subgraph Shared["JocysCom.ClassLibrary (embedded)"]
        Config["Configuration<br/>SettingsData, SettingsItem, AssemblyInfo"]
        CompModel["ComponentModel<br/>SortableBindingList, BindingListInvoked"]
        Controls["Controls<br/>ControlsHelper, ItemFormattingConverter,<br/>InfoControl, MessageBoxWindow"]
        Other["Collections, IO, Text, Runtime, Data"]
    end

    subgraph WinAPI["Windows OS"]
        User32["user32.dll"]
    end

    App --> MW --> DLC
    DLC --> DI
    DLC --> NM
    DLC --> CSV
    NM --> User32
    DI --> Config
    DLC --> CompModel
    DLC --> Controls
    MW --> Controls
```

### Key architectural decisions

- **Polling via timer:** A `System.Timers.Timer` with 1ms interval (non-auto-reset) continuously polls `GetActiveWindow()` and `GetForegroundWindow()`. Duplicate events are suppressed via `DataItem.IsSame()`.
- **Thread safety:** Timer fires on a thread-pool thread; UI updates are marshalled via `ControlsHelper.BeginInvoke()`. A `lock(AddLock)` synchronizes the polling logic.
- **Embedded shared library:** `JocysCom.ClassLibrary` files are included directly in `FocusLogger/JocysCom/` rather than as a compiled DLL or NuGet package.
- **No MVVM framework:** Code-behind pattern with data binding. `DataListControl.xaml.cs` contains both view-model-like logic and model interaction.

## 5. Project Inventory

This section lists each project in the solution with its key metadata.

### 5.1 JocysCom.FocusLogger (main application)

| Property | Value |
|----------|-------|
| Path | `FocusLogger/JocysCom.FocusLogger.csproj` |
| Output type | `WinExe` |
| Target framework | `net8.0-windows` |
| Assembly name | `JocysCom.FocusLogger` |
| Description | Find out which process or program is taking the window focus. In game, mouse and keyboard could temporarily stop responding if another program takes the focus. This tool could help diagnose which program is stealing the focus. |
| Version | 1.2.6 |
| NuGet dependencies | None |
| Embedded resources | `Resources/BuildDate.txt` (auto-generated), `Resources/AiAnalysisPrompt.md` |

**Source structure:**

| Directory | Contents |
|-----------|----------|
| `FocusLogger/` (root) | `App.xaml(.cs)`, `MainWindow.xaml(.cs)`, `AssemblyInfo.cs`, `App.ico` |
| `FocusLogger/Common/` | `DataItem.cs`, `DataItemType.cs`, `NativeMethods.cs` |
| `FocusLogger/Controls/` | `DataListControl.xaml(.cs)` — core logging control |
| `FocusLogger/JocysCom/` | Embedded `JocysCom.ClassLibrary` (~30 files across Collections, Common, ComponentModel, Configuration, Controls, Data, IO, Runtime, Text) |
| `FocusLogger/Resources/` | `AiAnalysisPrompt.md`, `BuildDate.txt`, `Icons/` (SVG sources, XAML icons, conversion scripts) |
| `FocusLogger/Properties/` | Publish profiles |

### 5.2 JocysCom.FocusLogger.Tests (test project)

| Property | Value |
|----------|-------|
| Path | `FocusLogger.Tests/JocysCom.FocusLogger.Tests.csproj` |
| Target framework | `net8.0-windows` |
| Test framework | MSTest v3.x |
| Project reference | `FocusLogger/JocysCom.FocusLogger.csproj` |

**Test files:**

| File | Purpose |
|------|---------|
| `CsvExportTests.cs` | Unit tests for `CsvEscape` and `BuildCsvContent` methods |
| `UIAutomationTests.cs` | UI automation tests using `System.Windows.Automation` — launches the built app and interacts with controls by AutomationId |

Run tests with: `dotnet test FocusLogger.Tests/JocysCom.FocusLogger.Tests.csproj`

## 6. Dependency & Data Flow

This section explains how the projects and components relate to each other and how data moves through the system.

### Project dependency graph

```mermaid
graph LR
    Tests["FocusLogger.Tests<br/>(MSTest v3)"] -->|ProjectReference| App["JocysCom.FocusLogger<br/>(WPF App)"]
    App -->|embedded source| Shared["JocysCom.ClassLibrary<br/>(in FocusLogger/JocysCom/)"]
    App -->|P/Invoke| WinAPI["user32.dll"]
```

### Runtime data flow

1. `System.Timers.Timer` fires (1ms interval, non-auto-reset).
2. `DataListControl.UpdateInfo()` acquires `AddLock`.
3. Calls `NativeMethods.GetActiveWindow()` and `NativeMethods.GetForegroundWindow()`.
4. For each handle, `GetItemFromHandle()` creates a `DataItem` with timestamp, focus flags (mouse/keyboard/caret), window title, and window class name.
5. `IsSame()` checks if the event differs from the previous one; if not, it is skipped.
6. `UpdateFromProcess()` enriches the `DataItem` with process name and path (with error handling for restricted processes).
7. The item is inserted at position 0 of `SortableBindingList<DataItem>` via `ControlsHelper.BeginInvoke()` (UI thread dispatch).
8. The WPF `DataGrid` updates via data binding. `ItemFormattingConverter` translates boolean flags to icons.

### CSV export flow

1. User clicks "Save CSV" button.
2. `SaveFileDialog` prompts for file location.
3. `BuildCsvContent()` iterates all `DataItem` entries, writing CSV with headers: Date, PID, Process Name, Active, Mouse, Keyboard, Caret, Window Title, Window Class, Path.
4. File is written as UTF-8.
5. "Explore" button opens the saved file location in Explorer.
6. "AI Prompt Example" button shows the embedded `AiAnalysisPrompt.md` in a `MessageBoxWindow` for users to copy and paste into an AI assistant along with their CSV.

## 7. Build, Test, CI/CD & Operational Workflows

This section documents how the project is built, tested, and released based on repository evidence.

### Build

```bash
dotnet build JocysCom.FocusLogger.slnx
```

- **Pre-build event:** Generates `Resources/BuildDate.txt` with the current ISO 8601 timestamp via PowerShell.
- **Output:** Single `JocysCom.FocusLogger.exe` in `bin/{Configuration}/net8.0-windows/`.
- **Debug configuration:** Embedded PDB symbols (`DebugType: embedded`).

### Test

```bash
dotnet test FocusLogger.Tests/JocysCom.FocusLogger.Tests.csproj
```

- **Framework:** MSTest v3.x with Microsoft.NET.Test.Sdk 17.x.
- **Unit tests:** `CsvExportTests` — validates CSV escaping and content generation.
- **UI automation tests:** `UIAutomationTests` — launches the built application and interacts via `System.Windows.Automation`. Requires a prior build of the main project.

### Release / packaging scripts

| Script | Purpose |
|--------|---------|
| `Documents/App_1_Sign.ps1` | Code-signs the application executable. |
| `Documents/App_2_Zip.ps1` | Packages the signed executable into a release ZIP. |
| `Resources/ZipFiles.ps1` | Shared utility for checksum-aware ZIP creation (compares source/dest checksums before rebuilding). |
| `Documents/Take_Screenshot.ps1` | Captures application screenshot for documentation. |
| `Documents/Take_Screenshot.ps1.cs` | C# helper compiled by the screenshot script. |
| `Solution_Cleanup.ps1` | Cleans `bin/`, `obj/`, and other build artifacts. |

### Icon workflow

SVG icon sources are stored in `FocusLogger/Resources/Icons/Icons_Default/`. The script `Convert_SVG_to_XAML.ps1` converts them to XAML resource dictionaries (`Icons_Default.xaml`).

### CI/CD

No CI/CD workflow files were found under `.github/workflows/`. Builds and releases appear to be performed locally.

## 8. Documentation Map

This section identifies where documentation lives in the repository.

| Location | Audience | Content |
|----------|----------|---------|
| `README.md` | End users, contributors | Project overview, download link, system requirements, screenshot |
| `SECURITY.md` | Security researchers | Vulnerability reporting policy |
| `LICENSE` | All | GPLv3 full text |
| `.ai/ReadMe.md` | AI agents, developers | Explains the purpose of each file in the `.ai/` directory and how custom instructions work for Copilot, CLINE, and Codex |
| `.ai/instructions.md` | AI agents | Role definition and output formatting rules for AI-assisted edits |
| `.ai/coding-guideline.instructions.md` | AI agents | Detailed coding guidelines, source control conventions (branch/PR naming), testing workflow, and constraints for AI agents |
| `.ai/repository-analysis.instructions.md` | AI agents, developers | This file — comprehensive repository reference |
| `.ai/skills/` | AI agents | Skill definitions (e.g., `ai-self-improvement`) for agent-assisted workflows |
| `FocusLogger/Resources/AiAnalysisPrompt.md` | End users | Prompt template for users to paste into AI assistants alongside exported CSV logs |
| `Documents/Images/` | README, users | Application screenshot |
| `Settings.XamlStyler` | Developers | XamlStyler formatting configuration |

### Documentation taxonomy

```mermaid
graph TD
    subgraph EndUsers["End-User Documentation"]
        README["README.md<br/>Overview, download, requirements"]
        SECURITY["SECURITY.md<br/>Vulnerability reporting"]
        LICENSE["LICENSE<br/>GPLv3"]
        AiPrompt["FocusLogger/Resources/<br/>AiAnalysisPrompt.md<br/>Prompt template for CSV analysis"]
        Screenshot["Documents/Images/<br/>Application screenshot"]
    end

    subgraph AIAgents["AI Agent Instructions"]
        AiReadMe[".ai/ReadMe.md<br/>Directory guide"]
        AiInstr[".ai/instructions.md<br/>Role & output rules"]
        AiCoding[".ai/coding-guideline<br/>.instructions.md<br/>Coding & SCM conventions"]
        AiRepo[".ai/repository-analysis<br/>.instructions.md<br/>This file"]
        AiSkills[".ai/skills/<br/>Agent skill definitions"]
    end

    subgraph DevConfig["Developer Configuration"]
        XamlStyler["Settings.XamlStyler<br/>XAML formatting"]
    end
```

## 9. AI-Agent-Relevant Conventions and Constraints

This section captures rules and patterns that materially affect automated edits. The full set of coding and source-control conventions is defined in `.ai/coding-guideline.instructions.md`; the highlights below are the items most likely to cause mistakes if overlooked.

1. **Coding style:** Follow Microsoft C# conventions. PascalCase for public members, camelCase for locals. Some private fields use `_PascalCase` (e.g., `_Date`). Preserve existing naming patterns in each file. Prefer the simplest viable solution; avoid over-engineering.

2. **Doc comments:** Per `.ai/instructions.md`, convert simple comments to XML documentation comments where beneficial for IntelliSense. Do not alter surrounding code when doing so.

3. **Shared library files (`FocusLogger/JocysCom/`):** These are embedded from a shared `JocysCom.ClassLibrary`. Exercise caution when editing — changes here may diverge from the upstream library.

4. **XAML formatting:** The repository uses XamlStyler (see `Settings.XamlStyler`). XAML edits should conform to the configured style.

5. **No NuGet packages in the main app:** All dependencies are framework-provided or embedded source. Do not introduce NuGet package dependencies without explicit approval.

6. **Test project uses MSTest v3:** New tests should follow MSTest v3 patterns (`[TestClass]`, `[TestMethod]`, `Assert.*`).

7. **UI automation tests depend on a built executable:** `UIAutomationTests` locate the app at a relative path from the test output. Building the main project before running these tests is required.

8. **Pre-build event:** The csproj generates `Resources/BuildDate.txt` via PowerShell. This file should not be manually edited or committed.

9. **Solution format:** Uses `.slnx` (XML-based solution format), not the older `.sln` text format.

10. **No CI/CD pipelines:** All build and release steps are manual/local. Scripts in `Documents/` handle signing and packaging.

11. **File size limit:** No code file that is created or modified may exceed 6000 tokens (~24 KB).

12. **Source control conventions:** Issues use `{CATEGORY}: {Description}` (FEAT, FIX, TECH, DOCS). Branches use `{CATEGORY}-{issue#}-{lowercase-dashed-name}`. PRs use `PR: #{issue#}: {CATEGORY}: {Description}` and must reference the issue with `Closes #{issue#}`. Merge via PR only — no direct pushes to `main`.

13. **No Co-Authored-By lines:** Do not add `Co-Authored-By` AI model/company lines to commits.

14. **Issue closure:** Never close issues before a release is published with the fix.

15. **No duplication / SSOT:** Update or move existing code instead of adding parallel implementations. If introducing a replacement, remove the old one in the same change.

16. **Stability primitives:** When the repo provides an established script or command, use it verbatim. Only deviate when it is proven broken, and then fix the primitive rather than inventing a parallel path.


================================================
FILE: .ai/skills/ai-self-improvement/SKILL.md
================================================
---
name: ai-self-improvement
description: Update, create, improve, and synchronise this repository's AI agent instructions and related assets (including skills). Use when the user asks to create or edit a skill/SKILL.md, modify the agent's own instructions/processes, restructure instruction governance, migrate instruction content into skills, or run/adjust the sync pipeline that publishes `.ai/` sources into agent-specific folders. Load this skill before writing any SKILL.md, .instructions.md, or touching any skills/ folder (.ai/, .claude/, .roo/, .github/). It tells you the correct location (.ai/) and the sync step, so files end up in the right place.
---

# AI Self-Improvement (Instructions + Skills)

## Critical: `.ai/` is the Primary Source for ALL Agents

The `.ai/` folder is the **single source of truth** for all AI agent configurations in this repository. This applies to:

- **CLINE / Roo Code** — synced to `.roo/rules/` and `.roo/skills/`
- **GitHub Copilot** — synced to `.github/copilot-instructions.md`
- **OpenAI Codex / AGENTS.md** — synced to `AGENTS.md` at repo root
- **Claude Code** — synced to `.claude/*.instructions.md` and `.claude/skills/`

**IMPORTANT:** When asked to modify skills, instructions, or perform any AI self-improvement task, you MUST:

1. Locate the source file under `.ai/` (not the agent-specific output)
2. Make changes to the `.ai/` source
3. Run the sync script to propagate changes to all agents

## Path Mapping Reference

When you encounter a path in an agent-specific folder, map it to `.ai/`:

| Agent-Specific Path | Source Path (Edit Here) |
|---------------------|------------------------|
| `.roo/rules/*.md` | `.ai/*.instructions.md` |
| `.roo/skills/<name>/SKILL.md` | `.ai/skills/<name>/SKILL.md` |
| `.github/copilot-instructions.md` | `.ai/instructions.md` (generated) |
| `AGENTS.md` | `.ai/instructions.md` (generated) |
| `.claude/*.instructions.md` | `.ai/*.instructions.md` |
| `.claude/skills/<name>/SKILL.md` | `.ai/skills/<name>/SKILL.md` |

**Example:** If asked to update `.roo/skills/ai-self-improvement/SKILL.md`, you must edit `.ai/skills/ai-self-improvement/SKILL.md` instead.

## Editable instruction files (sources of truth)

You can update your own instruction files under `.ai/`:

- `.ai/instructions.md` — the main system instructions file
- `.ai/*instructions.md` — additional instruction files (auto-included)
- `.ai/*instructions-detail.md` — detailed instruction files (read only when needed)
- `.ai/skills/<name>/SKILL.md` — skill definition files

## Workflow

1. Treat `.ai/` as the **single source of truth** for agent instructions **and skills**.
2. When creating or migrating a skill, create/update it under `.ai/skills/`.
3. Make instruction changes in `.ai/instructions.md` and related `*.instructions.md` / `*.instructions-detail.md` files.
4. Do **not** edit generated outputs directly (they are produced by the sync script):
   - `.roo/rules/`
   - `.roo/skills/`
   - `.github/copilot-instructions.md`
   - `AGENTS.md`
   - `.claude/`
5. **Test changes before syncing** — verify scripts execute correctly and changes work as expected.
6. After testing, run the sync script to apply to all agents.

## Testing Before Sync

Before running the sync script, always verify your changes work correctly:

- **For script changes**: Execute the modified script and verify output is correct
- **For instruction changes**: Review the markdown renders properly and instructions are clear
- **For skill changes**: Test any bundled tools or scripts included in the skill

**Example**: If you modify a PowerShell script in a skill, run it directly from `.ai/skills/<name>/scripts/` to confirm it works before syncing.

## Activation process

After editing instruction files (or master skills), run from repository root:

```powershell
.\.ai\skills\ai-self-improvement\scripts\Sync-AgentAssets.ps1 AUTO
```

This script synchronizes changes from `.ai/` to all agent-specific folders.

## Single source of truth

**Never embed template content in instructions — reference template files instead.**

Example:

- ✅ "Template maintained in `pr/checklist.template.md`"
- ❌ Pasting template content into instructions

## Bundled scripts

- Sync entrypoint (instructions + skills): `.ai/skills/ai-self-improvement/scripts/Sync-AgentAssets.ps1`


================================================
FILE: .ai/skills/ai-self-improvement/scripts/Sync-AgentAssets.ps1
================================================
# Script: Sync-AgentAssets.ps1
# Location: .ai/skills/ai-self-improvement/scripts/Sync-AgentAssets.ps1
# Description:
#   Synchronises AI agent instruction files and skills from master sources under `.ai/`.
#   - Instructions: copies `*.instructions.md` from `.ai/` into agent-specific outputs.
#   - Skills: mirrors `.ai/skills/*` into agent skill folders (e.g. `.roo/skills/*`).
#
# Options for Mode:
#   ALL  - update all known agent outputs
#   AUTO - update only agents that exist in this repository (default usage)
#   Or a specific agent name: CLINE, ROO CODE, GitHub CoPilot, OpenAI Codex, Claude Code

param(
    [Parameter(Position = 0)]
    [string]$Mode,

    [switch]$NoClear
)

# Combine remaining args so Windows PowerShell (-File) invocations like:
#   Sync-AgentAssets.ps1 GitHub CoPilot
# work the same as:
#   Sync-AgentAssets.ps1 "GitHub CoPilot"
if ($args.Count -gt 0) {
    $ModeFromArgs = ($args -join ' ')
    if (-not $Mode -or $Mode -eq '') {
        $Mode = $ModeFromArgs
    }
}

# Allow calling via the old filename (if invoked through a copied/renamed script).
# This only affects displayed script name in prompts/logs.
$scriptName = [System.IO.Path]::GetFileName($MyInvocation.MyCommand.Path)

# Strict mode
Set-StrictMode -Version Latest
$ErrorActionPreference = "Stop"

function Ensure-Directory {
    param(
        [Parameter(Mandatory = $true)]
        [string]$Path
    )

    if (-not (Test-Path -Path $Path -PathType Container)) {
        New-Item -ItemType Directory -Force -Path $Path | Out-Null
    }
}

# Function to check if instruction files exist in a directory
function Test-HasInstructionFiles {
    param(
        [Parameter(Mandatory = $true)]
        [string]$Path,
        [string]$Filter = '*instructions.md'
    )

    if (Test-Path $Path -PathType Container) {
        $files = @(Get-ChildItem $Path -Filter $Filter -File -ErrorAction SilentlyContinue)
        return ($files.Length -gt 0)
    }

    return $false
}

# Function to pause at the end (unless -NoWait is specified)
function Invoke-Pause {
    Write-Host "Pausing for 2 seconds..."
    Start-Sleep -Seconds 2
}

function Copy-FileIfDifferent {
    param(
        [Parameter(Mandatory = $true)]
        [string]$SourcePath,
        [Parameter(Mandatory = $true)]
        [string]$TargetPath
    )

    $targetDir = Split-Path -Path $TargetPath -Parent
    Ensure-Directory -Path $targetDir

    if (-not (Test-Path -Path $TargetPath -PathType Leaf)) {
        Copy-Item -LiteralPath $SourcePath -Destination $TargetPath -Force
        $relative = $TargetPath.Substring($repoRoot.Length + 1)
        Write-Host "Created: $relative"
        return
    }

    $srcBytes = [System.IO.File]::ReadAllBytes($SourcePath)
    $dstBytes = [System.IO.File]::ReadAllBytes($TargetPath)

    if ($srcBytes.Length -eq $dstBytes.Length) {
        $same = $true
        for ($i = 0; $i -lt $srcBytes.Length; $i++) {
            if ($srcBytes[$i] -ne $dstBytes[$i]) { $same = $false; break }
        }

        if ($same) {
            $relative = $TargetPath.Substring($repoRoot.Length + 1)
            Write-Host "Up-to-date: $relative"
            return
        }
    }

    Copy-Item -LiteralPath $SourcePath -Destination $TargetPath -Force
    $relative = $TargetPath.Substring($repoRoot.Length + 1)
    Write-Host "Updated: $relative"
}

function Get-TextAuto {
    param(
        [Parameter(Mandatory = $true)]
        [string]$Path
    )

    # .NET StreamReader detects BOM for UTF-8/UTF-16/UTF-32 automatically.
    $sr = New-Object System.IO.StreamReader($Path, $true)
    try {
        return $sr.ReadToEnd()
    }
    finally {
        $sr.Dispose()
    }
}

function Write-Utf8NoBom {
    param(
        [Parameter(Mandatory = $true)]
        [string]$Path,
        [Parameter(Mandatory = $true)]
        [string]$Content
    )

    $dir = Split-Path -Path $Path -Parent
    Ensure-Directory -Path $dir

    $utf8NoBom = New-Object System.Text.UTF8Encoding($false)
    [System.IO.File]::WriteAllText($Path, $Content, $utf8NoBom)
}

function Assert-InstructionSync {
    param(
        [Parameter(Mandatory = $true)]
        [string]$SourceDirectory,
        [Parameter(Mandatory = $true)]
        [string]$TargetDirectory,
        [Parameter(Mandatory = $true)]
        [System.IO.FileSystemInfo[]]$SourceFiles
    )

    $srcDir = Join-Path $repoRoot $SourceDirectory
    $dstDir = Join-Path $repoRoot $TargetDirectory

    foreach ($sourceFile in $SourceFiles) {
        $srcPath = Join-Path $srcDir $sourceFile.Name
        $dstPath = Join-Path $dstDir $sourceFile.Name

        if (-not (Test-Path $dstPath -PathType Leaf)) {
            throw "Binary comparison failed. Destination file missing: $dstPath"
        }

        $srcBytes = [System.IO.File]::ReadAllBytes($srcPath)
        $dstBytes = [System.IO.File]::ReadAllBytes($dstPath)

        if ($srcBytes.Length -ne $dstBytes.Length) {
            throw "Binary comparison failed. Source and target size mismatch in binary: Source: $srcPath Target: $dstPath"
        }

        for ($i = 0; $i -lt $srcBytes.Length; $i++) {
            if ($srcBytes[$i] -ne $dstBytes[$i]) {
                throw "Binary comparison failed. Source and target content mismatch in binary: Source: $srcPath Target: $dstPath"
            }
        }
    }
}

# Function to update agents that use multiple separate instruction files
function Update-MultipleFileAgent {
    param(
        [Parameter(Mandatory = $true)]
        [string]$AgentName,
        [Parameter(Mandatory = $true)]
        [string]$TargetDirectory,
        [Parameter(Mandatory = $true)]
        [System.IO.FileSystemInfo[]]$SourceFiles,
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    Write-Host "`r`n--- Updating $AgentName Instructions ---"
    $targetDir = Join-Path $RepoRoot $TargetDirectory

    foreach ($sourceFile in $SourceFiles) {
        $targetFile = Join-Path $targetDir $sourceFile.Name
        Copy-FileIfDifferent -SourcePath $sourceFile.FullName -TargetPath $targetFile
    }

    Assert-InstructionSync -SourceDirectory ".ai" -TargetDirectory $TargetDirectory -SourceFiles $SourceFiles
}

# Function to update agents that use a single combined instruction file
function Update-SingleFileAgent {
    param(
        [Parameter(Mandatory = $true)]
        [string]$AgentName,
        [Parameter(Mandatory = $true)]
        [string]$TargetFilePath,
        [Parameter(Mandatory = $true)]
        [System.IO.FileSystemInfo[]]$SourceFiles,
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    Write-Host "`r`n--- Updating $AgentName Instructions ---"
    $targetFile = Join-Path $RepoRoot $TargetFilePath
    $relativeTarget = $targetFile.Substring($repoRoot.Length + 1)

    $allInstructionsContent = New-Object System.Text.StringBuilder
    $firstFile = $true

    foreach ($sourceFile in $SourceFiles) {
        $sourceContent = Get-TextAuto -Path $sourceFile.FullName

        if ([string]::IsNullOrWhiteSpace($sourceContent)) {
            Write-Warning "Skipping empty file: $($sourceFile.Name)"
            continue
        }

        if (-not $firstFile) {
            [void]$allInstructionsContent.AppendLine("")
        }

        [void]$allInstructionsContent.AppendLine("==== START OF INSTRUCTIONS FROM: $($sourceFile.Name) ====")
        [void]$allInstructionsContent.AppendLine("")

        [void]$allInstructionsContent.AppendLine("# Instructions from: $($sourceFile.Name)")
        [void]$allInstructionsContent.AppendLine("")

        [void]$allInstructionsContent.AppendLine($sourceContent.Trim())

        [void]$allInstructionsContent.AppendLine("")
        [void]$allInstructionsContent.AppendLine("==== END OF INSTRUCTIONS FROM: $($sourceFile.Name) ====")

        $firstFile = $false
    }

    $finalContent = $allInstructionsContent.ToString()

    $existing = if (Test-Path -Path $targetFile -PathType Leaf) { Get-TextAuto -Path $targetFile } else { $null }
    if ($null -ne $existing -and $existing -eq $finalContent) {
        Write-Host "Up-to-date: $relativeTarget"
        return
    }

    Write-Utf8NoBom -Path $targetFile -Content $finalContent
    Write-Host "Updated: $relativeTarget"
}

function Invoke-RoboCopyMirror {
    param(
        [Parameter(Mandatory = $true)]
        [string]$SourceDirectory,
        [Parameter(Mandatory = $true)]
        [string]$DestinationDirectory,
        [Parameter(Mandatory = $true)]
        [string]$Label
    )

    if (-not (Test-Path $SourceDirectory -PathType Container)) {
        Write-Host "No skills folder found at: $SourceDirectory"
        return
    }

    Ensure-Directory -Path $DestinationDirectory

    Write-Host "`r`n--- Mirroring skills to $Label ---"
    Write-Host "Source:      $SourceDirectory"
    Write-Host "Destination: $DestinationDirectory"

    # /MIR      = mirror (copy + delete removed)
    # /FFT      = tolerate 2s timestamp granularity
    # /R:1 /W:1 = retry quickly
    # /NFL/NDL  = no file/dir listing (keep output compact)
    # /NJH/NJS  = no job header/summary
    # /NP       = no progress
    # /XD       = exclude version control/build dirs
    $excludedDirs = @('.git', '.vs', 'bin', 'obj')

    $args = @(
        $SourceDirectory,
        $DestinationDirectory,
        '/MIR',
        '/FFT',
        '/R:1',
        '/W:1',
        '/NFL',
        '/NDL',
        '/NJH',
        '/NJS',
        '/NP'
    )

    foreach ($d in $excludedDirs) {
        $args += '/XD'
        $args += $d
    }

    $exe = 'robocopy'
    # Do not echo the full robocopy command; it is noisy and can wrap in some terminals.
    Write-Host "robocopy <source> <destination> /MIR /NFL /NDL /NJH /NJS /NP ..."

    & $exe @args | Out-Null
    $exitCode = $LASTEXITCODE

    # Robocopy uses bitmask exit codes.
    # 0-7 are success with various flags; >= 8 indicates failure.
    if ($exitCode -ge 8) {
        throw "Robocopy failed with exit code $exitCode. Command: $cmd"
    }

    # IMPORTANT: robocopy returns 1+ for successful copies.
    # Ensure PowerShell script does not propagate a non-zero exit code for success cases.
    $global:LASTEXITCODE = 0

    Write-Host "Mirrored skills to $Label (robocopy exit code $exitCode)."
}

function Sync-SkillsToRoo {
    param(
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    $srcSkillsRoot = Join-Path $RepoRoot ".ai\skills"
    $rooSkillsRoot = Join-Path $RepoRoot ".roo\skills"

    Invoke-RoboCopyMirror -SourceDirectory $srcSkillsRoot -DestinationDirectory $rooSkillsRoot -Label "Roo (.roo\\skills)"
}

function Sync-SkillsToGitHub {
    param(
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    $srcSkillsRoot = Join-Path $RepoRoot ".ai\skills"
    $githubSkillsRoot = Join-Path $RepoRoot ".github\skills"

    Invoke-RoboCopyMirror -SourceDirectory $srcSkillsRoot -DestinationDirectory $githubSkillsRoot -Label "GitHub (.github\\skills)"
}

function Sync-SkillsToClaude {
    param(
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    $srcSkillsRoot = Join-Path $RepoRoot ".ai\skills"
    $claudeSkillsRoot = Join-Path $RepoRoot ".claude\skills"

    Invoke-RoboCopyMirror -SourceDirectory $srcSkillsRoot -DestinationDirectory $claudeSkillsRoot -Label "Claude Code (.claude\\skills)"
}

# --- Main Script ---
if (-not $NoClear) {
    Clear-Host
}

# We are located under `.ai/skills/<skill>/tools`. Find repo root by going up 4 levels.
$scriptDir = $PSScriptRoot
$repoRoot = (Join-Path -Path $scriptDir -ChildPath "..\..\..\.." | Resolve-Path).Path

# `.ai` folder path
$aiDir = Join-Path $repoRoot ".ai"

# Discover source files matching *instructions.md in the .ai folder
[System.IO.FileSystemInfo[]]$sourceInstructionFiles = Get-ChildItem -Path $aiDir -Filter "*instructions.md" -File | Sort-Object Name

if ($null -eq $sourceInstructionFiles -or $sourceInstructionFiles.Length -eq 0) {
    Write-Warning "No '*instructions.md' files found in '$aiDir'. Nothing to process."
    exit 0
}

Write-Host "Found the following source instruction files in '$aiDir':"
$sourceInstructionFiles | ForEach-Object { Write-Host "- $($_.Name)" }

# Mode parameter handling: if 'ALL' or 'AUTO', skip interactive prompt
if ($Mode -eq 'ALL') {
    Write-Host "Selected: ALL (parameter mode)"
    $updateCline = $true
    $updateCopilot = $true
    $updateRooCode = $true
    $updateCodex = $true
    $updateClaude = $true
}
elseif ($Mode -eq 'AUTO') {
    Write-Host "Selected: AUTO (parameter mode)"
    # Determine available agents based on instruction files
    $updateCline = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.clinerules')
    $updateRooCode = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.roo\rules')
    $updateCopilot = Test-Path (Join-Path $repoRoot '.github\copilot-instructions.md') -PathType Leaf
    $updateCodex = Test-Path (Join-Path $repoRoot 'AGENTS.md') -PathType Leaf
    $updateClaude = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.claude')
    Write-Host "Agents to update based on available instruction files:"
    if ($updateCline) { Write-Host "- CLINE" }
    if ($updateRooCode) { Write-Host "- ROO CODE" }
    if ($updateCopilot) { Write-Host "- GitHub CoPilot" }
    if ($updateCodex) { Write-Host "- OpenAI Codex" }
    if ($updateClaude) { Write-Host "- Claude Code" }
}
elseif ($Mode -and $Mode -ne '') {
    # Specific agent mode (e.g., CLINE, "ROO CODE", etc.)
    $updateCline = ($Mode -eq 'CLINE')
    $updateCopilot = ($Mode -eq 'GitHub CoPilot')
    $updateRooCode = ($Mode -eq 'ROO CODE')
    $updateCodex = ($Mode -eq 'OpenAI Codex')
    $updateClaude = ($Mode -eq 'Claude Code')
    Write-Host "Selected: $Mode (parameter mode)"
}
else {
    # User prompt for agent selection
    # Detect available agents for interactive menu
    $hasCline = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.clinerules')
    $hasRooCode = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.roo\rules')
    $hasCopilot = Test-Path (Join-Path $repoRoot '.github\copilot-instructions.md') -PathType Leaf
    $hasCodex = Test-Path (Join-Path $repoRoot 'AGENTS.md') -PathType Leaf
    $hasClaude = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.claude')

    Write-Host "`r`nDetected AI agents with instruction files:"
    if ($hasCline) { Write-Host "- CLINE" }
    if ($hasRooCode) { Write-Host "- ROO CODE" }
    if ($hasCopilot) { Write-Host "- GitHub CoPilot" }
    if ($hasCodex) { Write-Host "- OpenAI Codex" }
    if ($hasClaude) { Write-Host "- Claude Code" }

    Write-Host ""
    Write-Host "=============================================================="
    Write-Host "Select Agent Instruction Set to Update"
    Write-Host "--------------------------------------------------------------"
    Write-Host "1. AUTO           - Update only agents with instruction files (default)"
    Write-Host "2. ALL            - Update instructions for all AI agents"
    Write-Host "3. CLINE          - Update instructions for CLINE"
    Write-Host "4. ROO CODE       - Update instructions for ROO CODE"
    Write-Host "5. GitHub CoPilot - Update instructions for GitHub CoPilot"
    Write-Host "6. OpenAI Codex   - Update instructions for OpenAI Codex"
    Write-Host "7. Claude Code    - Update instructions for Claude Code"
    Write-Host "0. Exit"
    Write-Host "=============================================================="
    $selection = Read-Host "Enter the number of your choice (0-7)"

    # Initialize flags
    $updateCline = $false
    $updateCopilot = $false
    $updateRooCode = $false
    $updateCodex = $false
    $updateClaude = $false

    switch ($selection) {
        '1' {
            $updateCline = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.clinerules')
            $updateRooCode = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.roo\rules')
            $updateCopilot = Test-Path (Join-Path $repoRoot '.github\copilot-instructions.md') -PathType Leaf
            $updateCodex = Test-Path (Join-Path $repoRoot 'AGENTS.md') -PathType Leaf
            $updateClaude = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.claude')
            Write-Host "Selected: AUTO"
        }
        '2' {
            $updateCline = $true
            $updateCopilot = $true
            $updateRooCode = $true
            $updateCodex = $true
            $updateClaude = $true
            Write-Host "Selected: ALL"
        }
        '3' { $updateCline = $true; Write-Host "Selected: CLINE" }
        '4' { $updateRooCode = $true; Write-Host "Selected: ROO CODE" }
        '5' { $updateCopilot = $true; Write-Host "Selected: GitHub CoPilot" }
        '6' { $updateCodex = $true; Write-Host "Selected: OpenAI Codex" }
        '7' { $updateClaude = $true; Write-Host "Selected: Claude Code" }
        '0' { Write-Host "Operation cancelled by user."; exit 0 }
        default { throw "Invalid selection. Exiting." }
    }
}

# --- Multiple-File Agent Updates ---
if ($updateCline) {
    Update-MultipleFileAgent -AgentName "CLINE" -TargetDirectory ".clinerules" -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
}

if ($updateRooCode) {
    Update-MultipleFileAgent -AgentName "ROO CODE" -TargetDirectory ".roo\rules" -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
}

# --- Single-File Agent Updates ---
if ($updateCopilot) {
    $copilotTarget = ".github\copilot-instructions.md"
    $githubInstructionsDir = Join-Path $repoRoot ".github\instructions"

    if (Test-Path $githubInstructionsDir -PathType Container) {
        Write-Host "`r`n--- Updating GitHub CoPilot Instructions (folder-based) ---"

        $mainName = "instructions.md"
        $mainSource = $sourceInstructionFiles | Where-Object { $_.Name -ieq $mainName } | Select-Object -First 1
        if ($null -eq $mainSource) {
            throw "Expected source '$mainName' under .ai but none found."
        }

        Copy-FileIfDifferent -SourcePath $mainSource.FullName -TargetPath (Join-Path $repoRoot $copilotTarget)

        foreach ($sf in $sourceInstructionFiles) {
            if ($sf.Name -ieq $mainName) {
                continue
            }

            $destination = Join-Path $githubInstructionsDir $sf.Name
            Copy-FileIfDifferent -SourcePath $sf.FullName -TargetPath $destination
        }
    }
    else {
        Update-SingleFileAgent -AgentName "GitHub CoPilot" -TargetFilePath $copilotTarget -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
    }
}

if ($updateCodex) {
    Update-SingleFileAgent -AgentName "OpenAI Codex" -TargetFilePath "AGENTS.md" -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
}

# --- Claude Code (multiple-file agent) ---
if ($updateClaude) {
    Update-MultipleFileAgent -AgentName "Claude Code" -TargetDirectory ".claude" -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
}

# --- Skills mirroring ---
if ($updateRooCode -or $Mode -eq 'ALL' -or $Mode -eq 'AUTO') {
    Sync-SkillsToRoo -RepoRoot $repoRoot
}

# GitHub Copilot: mirror skills to `.github/skills` (Copilot tries to load from there).
if ($updateCopilot -or $Mode -eq 'ALL' -or $Mode -eq 'AUTO') {
    Sync-SkillsToGitHub -RepoRoot $repoRoot
}

# Claude Code: mirror skills to `.claude/skills`.
if ($updateClaude -or $Mode -eq 'ALL' -or $Mode -eq 'AUTO') {
    Sync-SkillsToClaude -RepoRoot $repoRoot
}

Write-Host "`r`nAll selected operations completed successfully."

# Only pause when launched by double-click (Explorer). In CI / terminal usage, do not pause.
if ($Host.Name -and $Host.Name -notlike '*ConsoleHost*') {
    Invoke-Pause
}


================================================
FILE: .claude/coding-guideline.instructions.md
================================================
# Coding Guidelines

- If the qdrant-mcp-server is running, use it for all permanent memory operations (e.g. storing user information).
- After making changes, ALWAYS start a new server for testing.
- Kill all existing related servers from previous testing before starting a new server.
- Prefer the simplest viable solution; avoid over-engineering.
- Do not add broad try/catch or wrapper layers unless required by a failing test or explicit requirement; if you catch, rethrow to preserve the stack.
- Before writing new code, actively look for existing utilities or functions that can be reused instead of duplicated.
- New helper methods or classes must be justified with a clear, documented need for functionality that is unavailable elsewhere in the codebase.
- Always iterate on and reuse existing code instead of creating new implementations.
- Avoid adding layers of abstraction that do not deliver clear value.
- Do not drastically change established patterns before iterating on them.
- No duplication / SSOT: update or move existing code instead of adding parallel implementations. If you introduce a replacement, remove the old one **in the same change**.
- Write code that accounts for different environments (dev, test, and prod).
- Only modify what is explicitly requested or clearly necessary; do **not** create new files or modules unless explicitly requested.
- When fixing bugs, exhaust current implementations before introducing new patterns; if new methods are used, remove the old ones.
- Keep the codebase clean and organized.
- Avoid one-off scripts unless absolutely necessary.
- Use mocks only for tests, not for dev or prod.
- Never add stubbing or fake data in dev or prod environments.
- Never overwrite the .env file without explicit confirmation.
- Focus solely on areas relevant to the task; leave unrelated code untouched.
- Write thorough tests for all major functionality.
- Avoid major changes to the existing architecture unless explicitly instructed.
- Always consider the impact on other methods and areas of the code.
- Prefer to wrap long lines for better readability.
- Preserve existing formatting; limit formatting to lines you changed and match surrounding style. Also remove any unused imports/usings or dead code **introduced by your edits**.
- Stability primitives (repeatability > cleverness): when the repo provides an established way to perform an operation (repo-owned script, documented command snippet, standard PS1 under .ai/Scripts), treat it as the single source of truth. Use it verbatim instead of synthesizing “equivalent” commands. Only deviate when explicitly asked or when the primitive is proven broken in this environment (and then fix the primitive, not invent a parallel path).
- No code file that you **create or modify** may exceed **6000 tokens (~24 KB)** once your changes are applied.
  - If your changes alone would push the file past this limit, either trim the change or ask for explicit permission to refactor; do **not** alter unrelated code solely to meet the limit.
  - Existing oversized files are left untouched unless the user explicitly requests a refactor.

## Source Control Conventions

Naming conventions for issues, branches, and pull requests.

### Categories

| Category | Use for |
|----------|---------|
| `FEAT`   | New features |
| `FIX`    | Bug fixes |
| `TECH`   | Infrastructure, dependencies, refactoring |
| `DOCS`   | Documentation |

### Naming Patterns

| Item       | Pattern | Example |
|------------|---------|---------|
| **Issue**  | `{CATEGORY}: {Description}` | `FEAT: Download logs to CSV` |
| **Branch** | `{CATEGORY}-{issue#}-{lowercase-dashed-name}` | `FEAT-21-download-logs-to-csv` |
| **PR**     | `PR: #{issue#}: {CATEGORY}: {Description}` | `PR: #21: FEAT: Download logs to CSV` |

- Branch names: lowercase, words separated by dashes, non-ASCII replaced with a single dash, derived from issue title but may be shortened.
- PR body must reference the issue with `Closes #{issue#}`.
- Merge via PR only — no direct pushes to `main` or `master`.
- Feature branches are always created from `main` or `master`. Never merge one feature branch into another — only merge `main` if you need to catch up.
- Always create branches from latest origin/main or origin/main, never merge sub-branches, confirm before risky git ops.
- Do not add Co-Authored-By {AI model}/{AI company} lines to commits.
- Never close issues before a release is published with the fix.

Use the following guidelines:

1. Doc Comment Enhancement for IntelliSense

    - Replace or augment simple comments with relevant doc comment syntax that is supported by IntelliSense as needed.
    - Preserve the original intent and wording of existing comments wherever possible.

2. Code Layout for Clarity

    - Place the most important or user-editable sections at the top if logically appropriate.
    - Insert headings or separators within the code to clearly delineate where customizations or key logic sections can be adjusted.

3. No Extraneous Code Comments

    - Do not include "one-off" or user-directed commentary in the code.
    - Confine all clarifications or additional suggestions to explanations outside of the code snippet.

4. Avoid Outdated or Deprecated Methods

    - Refrain from introducing or relying on obsolete or deprecated methods and libraries.
    - If the current code relies on potentially deprecated approaches, ask for clarification or provide viable, modern alternatives that align with best practices.

5. Testing and Validation

    - Suggest running unit tests or simulations on the modified segments to confirm that the changes fix the issue without impacting overall functionality.
    - Ensure that any proposed improvements, including doc comment upgrades, integrate seamlessly with the existing codebase.
    - After all code modifications, navigate to the affected project directory and build C# then Angular to confirm the application compiles without errors:
		cd {PROJECT} && dotnet build {PROJECT}.csproj
		cd {PROJECT}/ClientApp && ng build
    - Run relevant unit tests if code changes affect core logic.
    - If the developer certificate is not trusted, then execute: dotnet dev-certs https --trust
    - To launch project use: dotnet watch run --project {PROJECT}/{PROJECT}.csproj --launch-profile "{PROJECT} (NG Build)"

6. Rationale and Explanation

    - For every change (including comment conversions), provide a concise explanation detailing how the modification resolves the identified issue while preserving the original design and context.
    - Clearly highlight only the modifications made, ensuring that no previously validated progress is altered.
    - NOTE: Summarize reasoning for the user, but do NOT expose full chain-of-thought. Keep internal deliberations internal; surface only the concise rationale needed to justify each change.

7. Contextual Analysis

    - Use all available context—such as code history, inline documentation, style guidelines—to understand the intended functionality.
    - When inspecting an existing file for understanding, prefer reading the whole file in a
      single `read_file` call when it comfortably fits in context; switch to targeted slices
      only when the file is too large, the tool truncates it, or a specific anchor line is
      already known.
    - If the role or intent behind a code segment is ambiguous, ask for clarification rather than making assumptions.

8. Targeted, Incremental Changes

    - Identify and isolate only the problematic code segments (including places where IntelliSense doc comments can replace simple comments).
    - Provide minimal code snippets that address the issue without rewriting larger sections.
    - For each suggested code change, explicitly indicate the exact location in the code (e.g., by specifying the function name, class name, line number, or section heading) where the modification should be implemented.

9. Preservation of Context

    - Maintain all developer comments, annotations, and workarounds exactly as they appear, transforming them to doc comment format only when it improves IntelliSense support.
    - Do not modify or remove any non-code context unless explicitly instructed.
    - Avoid introducing new, irrelevant comments in the code.

10. Launching {PROJECT} Correctly:
    - Navigate to the {PROJECT} project folder.
    - Run the following command to launch the project with live reload and proper debugging configuration:
      dotnet watch run --launch-profile "{PROJECT} (NG Build)" --project {PROJECT}/{PROJECT}.csproj
    - This command will start the {PROJECT} project on the designated debugging session URL.
    - Ensure that any previous {PROJECT} instances are terminated before running this command.


================================================
FILE: .claude/instructions.md
================================================
## Role

Your role is to analyze and improve code by making only localized, targeted changes. You must preserve all validated code, comments, and documented workarounds exactly as they appear. Your suggestions should strictly address only the specific issues identified—such as upgrading simple comments to doc comments for IntelliSense—without altering any surrounding context. Additionally, ensure that no obsolete or deprecated methods are introduced during the improvement process, and do not add extraneous comments that do not directly contribute to the code’s logic. Furthermore, ensure code snippets are clearly structured for readability, placing important or user-editable sections at the top when logical, and using clear separators or headings to highlight customization points.
Wherever beneficial, convert simple comments into recognized documentation comment syntax (e.g., JSDoc for JavaScript, XML comments for C#, JavaDoc for Java) that can be parsed by code intelligence tools like IntelliSense.
Maintain the original meaning of these comments, but structure them in a way that provides maximum benefit for automated tools and refactoring methods.
Apply chain-of-thought reasoning to identify code segments best served by doc comments, analyze the existing context of each comment, and then make precise, incremental modifications that enhance IntelliSense compatibility while preserving existing functionality.

## Output

Wrap any and all code—including regular code snippets, inline code segments, outputs, pseudocode, or any text that represents code—in Markdown code blocks with a language identifier (e.g., ```typescript, ```powershell).


================================================
FILE: .claude/repository-analysis.instructions.md
================================================
# Repository Analysis

## 1. Repository Overview

This document provides a factual reference for the Jocys.com FocusLogger repository, aimed at developers and AI coding agents working on the codebase.

**FocusLogger** is a Windows desktop utility that monitors and logs which process or program takes window focus. It targets users (especially gamers and power users) who experience unexpected focus stealing — where a background process briefly grabs foreground focus, interrupting gameplay or work. The tool logs every focus change with timestamps, process details, window class names, and focus-state flags, allowing users to identify the culprit.

- **Repository:** https://github.com/JocysCom/FocusLogger
- **License:** GNU General Public License v3.0
- **Current version:** 1.2.6
- **Target platform:** Windows 10+ with .NET 8.0
- **Primary audiences:** Gamers, power users, IT support personnel diagnosing focus-stealing issues.

## 2. Top-Level Structure

This section maps every top-level directory and file to help navigate the repository quickly.

| Path | Purpose |
|------|---------|
| `FocusLogger/` | Main application project (WPF, .NET 8.0). Contains all app source code, shared library, and resources. |
| `FocusLogger.Tests/` | MSTest test project. Unit tests for CSV export and UI automation tests. |
| `Documents/` | Release engineering: signing scripts, zip packaging scripts, screenshot tooling, and pre-built release files. |
| `Resources/` | Solution-level shared scripts (currently `ZipFiles.ps1` for checksum-aware zip packaging). |
| `.ai/` | AI agent instructions, coding guidelines, repository analysis, and skills. |
| `JocysCom.FocusLogger.slnx` | Solution file (XML-based `.slnx` format) referencing the two projects. |
| `README.md` | Project overview, download link, system requirements, screenshot. |
| `LICENSE` | GPLv3 license text. |
| `SECURITY.md` | Security vulnerability reporting policy (support@jocys.com). |
| `Settings.XamlStyler` | XamlStyler configuration for consistent XAML formatting. |
| `Solution_Cleanup.ps1` | PowerShell script for cleaning build artifacts. |

## 3. Technology Stack & Key Dependencies

This section lists verified technologies and versions drawn from project files.

| Technology | Version / Detail | Evidence |
|------------|-----------------|----------|
| .NET | 8.0 (`net8.0-windows`) | `JocysCom.FocusLogger.csproj` TargetFramework |
| C# | Implicit (SDK default for .NET 8) | SDK-style project |
| WPF | `<UseWPF>true</UseWPF>` | csproj |
| Windows Forms interop | `<UseWindowsForms>true</UseWindowsForms>` | csproj — used for P/Invoke helpers and DPI awareness |
| MSTest | v3.x (`MSTest.TestFramework 3.*`, `MSTest.TestAdapter 3.*`) | Test csproj PackageReference |
| Microsoft.NET.Test.Sdk | 17.x | Test csproj PackageReference |
| Windows API (user32.dll) | P/Invoke | `NativeMethods.cs` |
| PowerShell | Scripts for build, sign, zip, cleanup | `Documents/`, `Resources/`, root |
| XamlStyler | Config present | `Settings.XamlStyler` |

**No NuGet package dependencies** in the main application project — all functionality comes from .NET SDK and the embedded `JocysCom.ClassLibrary`.

## 4. Architecture & Runtime Model

This section describes how the application is structured and how it operates at runtime.

FocusLogger is a **single-executable WPF desktop application** that polls Windows API functions to detect focus changes. It does not persist log data between sessions (in-memory only) but provides CSV export for offline analysis.

### Architectural layers

```mermaid
graph TD
    subgraph UI["UI Layer (WPF)"]
        App["App.xaml.cs<br/>Entry point, DPI aware"]
        MW["MainWindow.xaml.cs<br/>Main window frame"]
        DLC["DataListControl.xaml.cs<br/>Core logging UI + logic"]
    end

    subgraph Core["Core Logic"]
        DI["DataItem.cs<br/>Log entry model"]
        DIT["DataItemType.cs<br/>Entry type enum"]
        NM["NativeMethods.cs<br/>P/Invoke declarations"]
        CSV["CSV Export<br/>BuildCsvContent, CsvEscape"]
    end

    subgraph Shared["JocysCom.ClassLibrary (embedded)"]
        Config["Configuration<br/>SettingsData, SettingsItem, AssemblyInfo"]
        CompModel["ComponentModel<br/>SortableBindingList, BindingListInvoked"]
        Controls["Controls<br/>ControlsHelper, ItemFormattingConverter,<br/>InfoControl, MessageBoxWindow"]
        Other["Collections, IO, Text, Runtime, Data"]
    end

    subgraph WinAPI["Windows OS"]
        User32["user32.dll"]
    end

    App --> MW --> DLC
    DLC --> DI
    DLC --> NM
    DLC --> CSV
    NM --> User32
    DI --> Config
    DLC --> CompModel
    DLC --> Controls
    MW --> Controls
```

### Key architectural decisions

- **Polling via timer:** A `System.Timers.Timer` with 1ms interval (non-auto-reset) continuously polls `GetActiveWindow()` and `GetForegroundWindow()`. Duplicate events are suppressed via `DataItem.IsSame()`.
- **Thread safety:** Timer fires on a thread-pool thread; UI updates are marshalled via `ControlsHelper.BeginInvoke()`. A `lock(AddLock)` synchronizes the polling logic.
- **Embedded shared library:** `JocysCom.ClassLibrary` files are included directly in `FocusLogger/JocysCom/` rather than as a compiled DLL or NuGet package.
- **No MVVM framework:** Code-behind pattern with data binding. `DataListControl.xaml.cs` contains both view-model-like logic and model interaction.

## 5. Project Inventory

This section lists each project in the solution with its key metadata.

### 5.1 JocysCom.FocusLogger (main application)

| Property | Value |
|----------|-------|
| Path | `FocusLogger/JocysCom.FocusLogger.csproj` |
| Output type | `WinExe` |
| Target framework | `net8.0-windows` |
| Assembly name | `JocysCom.FocusLogger` |
| Description | Find out which process or program is taking the window focus. In game, mouse and keyboard could temporarily stop responding if another program takes the focus. This tool could help diagnose which program is stealing the focus. |
| Version | 1.2.6 |
| NuGet dependencies | None |
| Embedded resources | `Resources/BuildDate.txt` (auto-generated), `Resources/AiAnalysisPrompt.md` |

**Source structure:**

| Directory | Contents |
|-----------|----------|
| `FocusLogger/` (root) | `App.xaml(.cs)`, `MainWindow.xaml(.cs)`, `AssemblyInfo.cs`, `App.ico` |
| `FocusLogger/Common/` | `DataItem.cs`, `DataItemType.cs`, `NativeMethods.cs` |
| `FocusLogger/Controls/` | `DataListControl.xaml(.cs)` — core logging control |
| `FocusLogger/JocysCom/` | Embedded `JocysCom.ClassLibrary` (~30 files across Collections, Common, ComponentModel, Configuration, Controls, Data, IO, Runtime, Text) |
| `FocusLogger/Resources/` | `AiAnalysisPrompt.md`, `BuildDate.txt`, `Icons/` (SVG sources, XAML icons, conversion scripts) |
| `FocusLogger/Properties/` | Publish profiles |

### 5.2 JocysCom.FocusLogger.Tests (test project)

| Property | Value |
|----------|-------|
| Path | `FocusLogger.Tests/JocysCom.FocusLogger.Tests.csproj` |
| Target framework | `net8.0-windows` |
| Test framework | MSTest v3.x |
| Project reference | `FocusLogger/JocysCom.FocusLogger.csproj` |

**Test files:**

| File | Purpose |
|------|---------|
| `CsvExportTests.cs` | Unit tests for `CsvEscape` and `BuildCsvContent` methods |
| `UIAutomationTests.cs` | UI automation tests using `System.Windows.Automation` — launches the built app and interacts with controls by AutomationId |

Run tests with: `dotnet test FocusLogger.Tests/JocysCom.FocusLogger.Tests.csproj`

## 6. Dependency & Data Flow

This section explains how the projects and components relate to each other and how data moves through the system.

### Project dependency graph

```mermaid
graph LR
    Tests["FocusLogger.Tests<br/>(MSTest v3)"] -->|ProjectReference| App["JocysCom.FocusLogger<br/>(WPF App)"]
    App -->|embedded source| Shared["JocysCom.ClassLibrary<br/>(in FocusLogger/JocysCom/)"]
    App -->|P/Invoke| WinAPI["user32.dll"]
```

### Runtime data flow

1. `System.Timers.Timer` fires (1ms interval, non-auto-reset).
2. `DataListControl.UpdateInfo()` acquires `AddLock`.
3. Calls `NativeMethods.GetActiveWindow()` and `NativeMethods.GetForegroundWindow()`.
4. For each handle, `GetItemFromHandle()` creates a `DataItem` with timestamp, focus flags (mouse/keyboard/caret), window title, and window class name.
5. `IsSame()` checks if the event differs from the previous one; if not, it is skipped.
6. `UpdateFromProcess()` enriches the `DataItem` with process name and path (with error handling for restricted processes).
7. The item is inserted at position 0 of `SortableBindingList<DataItem>` via `ControlsHelper.BeginInvoke()` (UI thread dispatch).
8. The WPF `DataGrid` updates via data binding. `ItemFormattingConverter` translates boolean flags to icons.

### CSV export flow

1. User clicks "Save CSV" button.
2. `SaveFileDialog` prompts for file location.
3. `BuildCsvContent()` iterates all `DataItem` entries, writing CSV with headers: Date, PID, Process Name, Active, Mouse, Keyboard, Caret, Window Title, Window Class, Path.
4. File is written as UTF-8.
5. "Explore" button opens the saved file location in Explorer.
6. "AI Prompt Example" button shows the embedded `AiAnalysisPrompt.md` in a `MessageBoxWindow` for users to copy and paste into an AI assistant along with their CSV.

## 7. Build, Test, CI/CD & Operational Workflows

This section documents how the project is built, tested, and released based on repository evidence.

### Build

```bash
dotnet build JocysCom.FocusLogger.slnx
```

- **Pre-build event:** Generates `Resources/BuildDate.txt` with the current ISO 8601 timestamp via PowerShell.
- **Output:** Single `JocysCom.FocusLogger.exe` in `bin/{Configuration}/net8.0-windows/`.
- **Debug configuration:** Embedded PDB symbols (`DebugType: embedded`).

### Test

```bash
dotnet test FocusLogger.Tests/JocysCom.FocusLogger.Tests.csproj
```

- **Framework:** MSTest v3.x with Microsoft.NET.Test.Sdk 17.x.
- **Unit tests:** `CsvExportTests` — validates CSV escaping and content generation.
- **UI automation tests:** `UIAutomationTests` — launches the built application and interacts via `System.Windows.Automation`. Requires a prior build of the main project.

### Release / packaging scripts

| Script | Purpose |
|--------|---------|
| `Documents/App_1_Sign.ps1` | Code-signs the application executable. |
| `Documents/App_2_Zip.ps1` | Packages the signed executable into a release ZIP. |
| `Resources/ZipFiles.ps1` | Shared utility for checksum-aware ZIP creation (compares source/dest checksums before rebuilding). |
| `Documents/Take_Screenshot.ps1` | Captures application screenshot for documentation. |
| `Documents/Take_Screenshot.ps1.cs` | C# helper compiled by the screenshot script. |
| `Solution_Cleanup.ps1` | Cleans `bin/`, `obj/`, and other build artifacts. |

### Icon workflow

SVG icon sources are stored in `FocusLogger/Resources/Icons/Icons_Default/`. The script `Convert_SVG_to_XAML.ps1` converts them to XAML resource dictionaries (`Icons_Default.xaml`).

### CI/CD

No CI/CD workflow files were found under `.github/workflows/`. Builds and releases appear to be performed locally.

## 8. Documentation Map

This section identifies where documentation lives in the repository.

| Location | Audience | Content |
|----------|----------|---------|
| `README.md` | End users, contributors | Project overview, download link, system requirements, screenshot |
| `SECURITY.md` | Security researchers | Vulnerability reporting policy |
| `LICENSE` | All | GPLv3 full text |
| `.ai/ReadMe.md` | AI agents, developers | Explains the purpose of each file in the `.ai/` directory and how custom instructions work for Copilot, CLINE, and Codex |
| `.ai/instructions.md` | AI agents | Role definition and output formatting rules for AI-assisted edits |
| `.ai/coding-guideline.instructions.md` | AI agents | Detailed coding guidelines, source control conventions (branch/PR naming), testing workflow, and constraints for AI agents |
| `.ai/repository-analysis.instructions.md` | AI agents, developers | This file — comprehensive repository reference |
| `.ai/skills/` | AI agents | Skill definitions (e.g., `ai-self-improvement`) for agent-assisted workflows |
| `FocusLogger/Resources/AiAnalysisPrompt.md` | End users | Prompt template for users to paste into AI assistants alongside exported CSV logs |
| `Documents/Images/` | README, users | Application screenshot |
| `Settings.XamlStyler` | Developers | XamlStyler formatting configuration |

### Documentation taxonomy

```mermaid
graph TD
    subgraph EndUsers["End-User Documentation"]
        README["README.md<br/>Overview, download, requirements"]
        SECURITY["SECURITY.md<br/>Vulnerability reporting"]
        LICENSE["LICENSE<br/>GPLv3"]
        AiPrompt["FocusLogger/Resources/<br/>AiAnalysisPrompt.md<br/>Prompt template for CSV analysis"]
        Screenshot["Documents/Images/<br/>Application screenshot"]
    end

    subgraph AIAgents["AI Agent Instructions"]
        AiReadMe[".ai/ReadMe.md<br/>Directory guide"]
        AiInstr[".ai/instructions.md<br/>Role & output rules"]
        AiCoding[".ai/coding-guideline<br/>.instructions.md<br/>Coding & SCM conventions"]
        AiRepo[".ai/repository-analysis<br/>.instructions.md<br/>This file"]
        AiSkills[".ai/skills/<br/>Agent skill definitions"]
    end

    subgraph DevConfig["Developer Configuration"]
        XamlStyler["Settings.XamlStyler<br/>XAML formatting"]
    end
```

## 9. AI-Agent-Relevant Conventions and Constraints

This section captures rules and patterns that materially affect automated edits. The full set of coding and source-control conventions is defined in `.ai/coding-guideline.instructions.md`; the highlights below are the items most likely to cause mistakes if overlooked.

1. **Coding style:** Follow Microsoft C# conventions. PascalCase for public members, camelCase for locals. Some private fields use `_PascalCase` (e.g., `_Date`). Preserve existing naming patterns in each file. Prefer the simplest viable solution; avoid over-engineering.

2. **Doc comments:** Per `.ai/instructions.md`, convert simple comments to XML documentation comments where beneficial for IntelliSense. Do not alter surrounding code when doing so.

3. **Shared library files (`FocusLogger/JocysCom/`):** These are embedded from a shared `JocysCom.ClassLibrary`. Exercise caution when editing — changes here may diverge from the upstream library.

4. **XAML formatting:** The repository uses XamlStyler (see `Settings.XamlStyler`). XAML edits should conform to the configured style.

5. **No NuGet packages in the main app:** All dependencies are framework-provided or embedded source. Do not introduce NuGet package dependencies without explicit approval.

6. **Test project uses MSTest v3:** New tests should follow MSTest v3 patterns (`[TestClass]`, `[TestMethod]`, `Assert.*`).

7. **UI automation tests depend on a built executable:** `UIAutomationTests` locate the app at a relative path from the test output. Building the main project before running these tests is required.

8. **Pre-build event:** The csproj generates `Resources/BuildDate.txt` via PowerShell. This file should not be manually edited or committed.

9. **Solution format:** Uses `.slnx` (XML-based solution format), not the older `.sln` text format.

10. **No CI/CD pipelines:** All build and release steps are manual/local. Scripts in `Documents/` handle signing and packaging.

11. **File size limit:** No code file that is created or modified may exceed 6000 tokens (~24 KB).

12. **Source control conventions:** Issues use `{CATEGORY}: {Description}` (FEAT, FIX, TECH, DOCS). Branches use `{CATEGORY}-{issue#}-{lowercase-dashed-name}`. PRs use `PR: #{issue#}: {CATEGORY}: {Description}` and must reference the issue with `Closes #{issue#}`. Merge via PR only — no direct pushes to `main`.

13. **No Co-Authored-By lines:** Do not add `Co-Authored-By` AI model/company lines to commits.

14. **Issue closure:** Never close issues before a release is published with the fix.

15. **No duplication / SSOT:** Update or move existing code instead of adding parallel implementations. If introducing a replacement, remove the old one in the same change.

16. **Stability primitives:** When the repo provides an established script or command, use it verbatim. Only deviate when it is proven broken, and then fix the primitive rather than inventing a parallel path.


================================================
FILE: .claude/skills/ai-self-improvement/SKILL.md
================================================
---
name: ai-self-improvement
description: Update, create, improve, and synchronise this repository's AI agent instructions and related assets (including skills). Use when the user asks to create or edit a skill/SKILL.md, modify the agent's own instructions/processes, restructure instruction governance, migrate instruction content into skills, or run/adjust the sync pipeline that publishes `.ai/` sources into agent-specific folders. Load this skill before writing any SKILL.md, .instructions.md, or touching any skills/ folder (.ai/, .claude/, .roo/, .github/). It tells you the correct location (.ai/) and the sync step, so files end up in the right place.
---

# AI Self-Improvement (Instructions + Skills)

## Critical: `.ai/` is the Primary Source for ALL Agents

The `.ai/` folder is the **single source of truth** for all AI agent configurations in this repository. This applies to:

- **CLINE / Roo Code** — synced to `.roo/rules/` and `.roo/skills/`
- **GitHub Copilot** — synced to `.github/copilot-instructions.md`
- **OpenAI Codex / AGENTS.md** — synced to `AGENTS.md` at repo root
- **Claude Code** — synced to `.claude/*.instructions.md` and `.claude/skills/`

**IMPORTANT:** When asked to modify skills, instructions, or perform any AI self-improvement task, you MUST:

1. Locate the source file under `.ai/` (not the agent-specific output)
2. Make changes to the `.ai/` source
3. Run the sync script to propagate changes to all agents

## Path Mapping Reference

When you encounter a path in an agent-specific folder, map it to `.ai/`:

| Agent-Specific Path | Source Path (Edit Here) |
|---------------------|------------------------|
| `.roo/rules/*.md` | `.ai/*.instructions.md` |
| `.roo/skills/<name>/SKILL.md` | `.ai/skills/<name>/SKILL.md` |
| `.github/copilot-instructions.md` | `.ai/instructions.md` (generated) |
| `AGENTS.md` | `.ai/instructions.md` (generated) |
| `.claude/*.instructions.md` | `.ai/*.instructions.md` |
| `.claude/skills/<name>/SKILL.md` | `.ai/skills/<name>/SKILL.md` |

**Example:** If asked to update `.roo/skills/ai-self-improvement/SKILL.md`, you must edit `.ai/skills/ai-self-improvement/SKILL.md` instead.

## Editable instruction files (sources of truth)

You can update your own instruction files under `.ai/`:

- `.ai/instructions.md` — the main system instructions file
- `.ai/*instructions.md` — additional instruction files (auto-included)
- `.ai/*instructions-detail.md` — detailed instruction files (read only when needed)
- `.ai/skills/<name>/SKILL.md` — skill definition files

## Workflow

1. Treat `.ai/` as the **single source of truth** for agent instructions **and skills**.
2. When creating or migrating a skill, create/update it under `.ai/skills/`.
3. Make instruction changes in `.ai/instructions.md` and related `*.instructions.md` / `*.instructions-detail.md` files.
4. Do **not** edit generated outputs directly (they are produced by the sync script):
   - `.roo/rules/`
   - `.roo/skills/`
   - `.github/copilot-instructions.md`
   - `AGENTS.md`
   - `.claude/`
5. **Test changes before syncing** — verify scripts execute correctly and changes work as expected.
6. After testing, run the sync script to apply to all agents.

## Testing Before Sync

Before running the sync script, always verify your changes work correctly:

- **For script changes**: Execute the modified script and verify output is correct
- **For instruction changes**: Review the markdown renders properly and instructions are clear
- **For skill changes**: Test any bundled tools or scripts included in the skill

**Example**: If you modify a PowerShell script in a skill, run it directly from `.ai/skills/<name>/scripts/` to confirm it works before syncing.

## Activation process

After editing instruction files (or master skills), run from repository root:

```powershell
.\.ai\skills\ai-self-improvement\scripts\Sync-AgentAssets.ps1 AUTO
```

This script synchronizes changes from `.ai/` to all agent-specific folders.

## Single source of truth

**Never embed template content in instructions — reference template files instead.**

Example:

- ✅ "Template maintained in `pr/checklist.template.md`"
- ❌ Pasting template content into instructions

## Bundled scripts

- Sync entrypoint (instructions + skills): `.ai/skills/ai-self-improvement/scripts/Sync-AgentAssets.ps1`


================================================
FILE: .claude/skills/ai-self-improvement/scripts/Sync-AgentAssets.ps1
================================================
# Script: Sync-AgentAssets.ps1
# Location: .ai/skills/ai-self-improvement/scripts/Sync-AgentAssets.ps1
# Description:
#   Synchronises AI agent instruction files and skills from master sources under `.ai/`.
#   - Instructions: copies `*.instructions.md` from `.ai/` into agent-specific outputs.
#   - Skills: mirrors `.ai/skills/*` into agent skill folders (e.g. `.roo/skills/*`).
#
# Options for Mode:
#   ALL  - update all known agent outputs
#   AUTO - update only agents that exist in this repository (default usage)
#   Or a specific agent name: CLINE, ROO CODE, GitHub CoPilot, OpenAI Codex, Claude Code

param(
    [Parameter(Position = 0)]
    [string]$Mode,

    [switch]$NoClear
)

# Combine remaining args so Windows PowerShell (-File) invocations like:
#   Sync-AgentAssets.ps1 GitHub CoPilot
# work the same as:
#   Sync-AgentAssets.ps1 "GitHub CoPilot"
if ($args.Count -gt 0) {
    $ModeFromArgs = ($args -join ' ')
    if (-not $Mode -or $Mode -eq '') {
        $Mode = $ModeFromArgs
    }
}

# Allow calling via the old filename (if invoked through a copied/renamed script).
# This only affects displayed script name in prompts/logs.
$scriptName = [System.IO.Path]::GetFileName($MyInvocation.MyCommand.Path)

# Strict mode
Set-StrictMode -Version Latest
$ErrorActionPreference = "Stop"

function Ensure-Directory {
    param(
        [Parameter(Mandatory = $true)]
        [string]$Path
    )

    if (-not (Test-Path -Path $Path -PathType Container)) {
        New-Item -ItemType Directory -Force -Path $Path | Out-Null
    }
}

# Function to check if instruction files exist in a directory
function Test-HasInstructionFiles {
    param(
        [Parameter(Mandatory = $true)]
        [string]$Path,
        [string]$Filter = '*instructions.md'
    )

    if (Test-Path $Path -PathType Container) {
        $files = @(Get-ChildItem $Path -Filter $Filter -File -ErrorAction SilentlyContinue)
        return ($files.Length -gt 0)
    }

    return $false
}

# Function to pause at the end (unless -NoWait is specified)
function Invoke-Pause {
    Write-Host "Pausing for 2 seconds..."
    Start-Sleep -Seconds 2
}

function Copy-FileIfDifferent {
    param(
        [Parameter(Mandatory = $true)]
        [string]$SourcePath,
        [Parameter(Mandatory = $true)]
        [string]$TargetPath
    )

    $targetDir = Split-Path -Path $TargetPath -Parent
    Ensure-Directory -Path $targetDir

    if (-not (Test-Path -Path $TargetPath -PathType Leaf)) {
        Copy-Item -LiteralPath $SourcePath -Destination $TargetPath -Force
        $relative = $TargetPath.Substring($repoRoot.Length + 1)
        Write-Host "Created: $relative"
        return
    }

    $srcBytes = [System.IO.File]::ReadAllBytes($SourcePath)
    $dstBytes = [System.IO.File]::ReadAllBytes($TargetPath)

    if ($srcBytes.Length -eq $dstBytes.Length) {
        $same = $true
        for ($i = 0; $i -lt $srcBytes.Length; $i++) {
            if ($srcBytes[$i] -ne $dstBytes[$i]) { $same = $false; break }
        }

        if ($same) {
            $relative = $TargetPath.Substring($repoRoot.Length + 1)
            Write-Host "Up-to-date: $relative"
            return
        }
    }

    Copy-Item -LiteralPath $SourcePath -Destination $TargetPath -Force
    $relative = $TargetPath.Substring($repoRoot.Length + 1)
    Write-Host "Updated: $relative"
}

function Get-TextAuto {
    param(
        [Parameter(Mandatory = $true)]
        [string]$Path
    )

    # .NET StreamReader detects BOM for UTF-8/UTF-16/UTF-32 automatically.
    $sr = New-Object System.IO.StreamReader($Path, $true)
    try {
        return $sr.ReadToEnd()
    }
    finally {
        $sr.Dispose()
    }
}

function Write-Utf8NoBom {
    param(
        [Parameter(Mandatory = $true)]
        [string]$Path,
        [Parameter(Mandatory = $true)]
        [string]$Content
    )

    $dir = Split-Path -Path $Path -Parent
    Ensure-Directory -Path $dir

    $utf8NoBom = New-Object System.Text.UTF8Encoding($false)
    [System.IO.File]::WriteAllText($Path, $Content, $utf8NoBom)
}

function Assert-InstructionSync {
    param(
        [Parameter(Mandatory = $true)]
        [string]$SourceDirectory,
        [Parameter(Mandatory = $true)]
        [string]$TargetDirectory,
        [Parameter(Mandatory = $true)]
        [System.IO.FileSystemInfo[]]$SourceFiles
    )

    $srcDir = Join-Path $repoRoot $SourceDirectory
    $dstDir = Join-Path $repoRoot $TargetDirectory

    foreach ($sourceFile in $SourceFiles) {
        $srcPath = Join-Path $srcDir $sourceFile.Name
        $dstPath = Join-Path $dstDir $sourceFile.Name

        if (-not (Test-Path $dstPath -PathType Leaf)) {
            throw "Binary comparison failed. Destination file missing: $dstPath"
        }

        $srcBytes = [System.IO.File]::ReadAllBytes($srcPath)
        $dstBytes = [System.IO.File]::ReadAllBytes($dstPath)

        if ($srcBytes.Length -ne $dstBytes.Length) {
            throw "Binary comparison failed. Source and target size mismatch in binary: Source: $srcPath Target: $dstPath"
        }

        for ($i = 0; $i -lt $srcBytes.Length; $i++) {
            if ($srcBytes[$i] -ne $dstBytes[$i]) {
                throw "Binary comparison failed. Source and target content mismatch in binary: Source: $srcPath Target: $dstPath"
            }
        }
    }
}

# Function to update agents that use multiple separate instruction files
function Update-MultipleFileAgent {
    param(
        [Parameter(Mandatory = $true)]
        [string]$AgentName,
        [Parameter(Mandatory = $true)]
        [string]$TargetDirectory,
        [Parameter(Mandatory = $true)]
        [System.IO.FileSystemInfo[]]$SourceFiles,
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    Write-Host "`r`n--- Updating $AgentName Instructions ---"
    $targetDir = Join-Path $RepoRoot $TargetDirectory

    foreach ($sourceFile in $SourceFiles) {
        $targetFile = Join-Path $targetDir $sourceFile.Name
        Copy-FileIfDifferent -SourcePath $sourceFile.FullName -TargetPath $targetFile
    }

    Assert-InstructionSync -SourceDirectory ".ai" -TargetDirectory $TargetDirectory -SourceFiles $SourceFiles
}

# Function to update agents that use a single combined instruction file
function Update-SingleFileAgent {
    param(
        [Parameter(Mandatory = $true)]
        [string]$AgentName,
        [Parameter(Mandatory = $true)]
        [string]$TargetFilePath,
        [Parameter(Mandatory = $true)]
        [System.IO.FileSystemInfo[]]$SourceFiles,
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    Write-Host "`r`n--- Updating $AgentName Instructions ---"
    $targetFile = Join-Path $RepoRoot $TargetFilePath
    $relativeTarget = $targetFile.Substring($repoRoot.Length + 1)

    $allInstructionsContent = New-Object System.Text.StringBuilder
    $firstFile = $true

    foreach ($sourceFile in $SourceFiles) {
        $sourceContent = Get-TextAuto -Path $sourceFile.FullName

        if ([string]::IsNullOrWhiteSpace($sourceContent)) {
            Write-Warning "Skipping empty file: $($sourceFile.Name)"
            continue
        }

        if (-not $firstFile) {
            [void]$allInstructionsContent.AppendLine("")
        }

        [void]$allInstructionsContent.AppendLine("==== START OF INSTRUCTIONS FROM: $($sourceFile.Name) ====")
        [void]$allInstructionsContent.AppendLine("")

        [void]$allInstructionsContent.AppendLine("# Instructions from: $($sourceFile.Name)")
        [void]$allInstructionsContent.AppendLine("")

        [void]$allInstructionsContent.AppendLine($sourceContent.Trim())

        [void]$allInstructionsContent.AppendLine("")
        [void]$allInstructionsContent.AppendLine("==== END OF INSTRUCTIONS FROM: $($sourceFile.Name) ====")

        $firstFile = $false
    }

    $finalContent = $allInstructionsContent.ToString()

    $existing = if (Test-Path -Path $targetFile -PathType Leaf) { Get-TextAuto -Path $targetFile } else { $null }
    if ($null -ne $existing -and $existing -eq $finalContent) {
        Write-Host "Up-to-date: $relativeTarget"
        return
    }

    Write-Utf8NoBom -Path $targetFile -Content $finalContent
    Write-Host "Updated: $relativeTarget"
}

function Invoke-RoboCopyMirror {
    param(
        [Parameter(Mandatory = $true)]
        [string]$SourceDirectory,
        [Parameter(Mandatory = $true)]
        [string]$DestinationDirectory,
        [Parameter(Mandatory = $true)]
        [string]$Label
    )

    if (-not (Test-Path $SourceDirectory -PathType Container)) {
        Write-Host "No skills folder found at: $SourceDirectory"
        return
    }

    Ensure-Directory -Path $DestinationDirectory

    Write-Host "`r`n--- Mirroring skills to $Label ---"
    Write-Host "Source:      $SourceDirectory"
    Write-Host "Destination: $DestinationDirectory"

    # /MIR      = mirror (copy + delete removed)
    # /FFT      = tolerate 2s timestamp granularity
    # /R:1 /W:1 = retry quickly
    # /NFL/NDL  = no file/dir listing (keep output compact)
    # /NJH/NJS  = no job header/summary
    # /NP       = no progress
    # /XD       = exclude version control/build dirs
    $excludedDirs = @('.git', '.vs', 'bin', 'obj')

    $args = @(
        $SourceDirectory,
        $DestinationDirectory,
        '/MIR',
        '/FFT',
        '/R:1',
        '/W:1',
        '/NFL',
        '/NDL',
        '/NJH',
        '/NJS',
        '/NP'
    )

    foreach ($d in $excludedDirs) {
        $args += '/XD'
        $args += $d
    }

    $exe = 'robocopy'
    # Do not echo the full robocopy command; it is noisy and can wrap in some terminals.
    Write-Host "robocopy <source> <destination> /MIR /NFL /NDL /NJH /NJS /NP ..."

    & $exe @args | Out-Null
    $exitCode = $LASTEXITCODE

    # Robocopy uses bitmask exit codes.
    # 0-7 are success with various flags; >= 8 indicates failure.
    if ($exitCode -ge 8) {
        throw "Robocopy failed with exit code $exitCode. Command: $cmd"
    }

    # IMPORTANT: robocopy returns 1+ for successful copies.
    # Ensure PowerShell script does not propagate a non-zero exit code for success cases.
    $global:LASTEXITCODE = 0

    Write-Host "Mirrored skills to $Label (robocopy exit code $exitCode)."
}

function Sync-SkillsToRoo {
    param(
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    $srcSkillsRoot = Join-Path $RepoRoot ".ai\skills"
    $rooSkillsRoot = Join-Path $RepoRoot ".roo\skills"

    Invoke-RoboCopyMirror -SourceDirectory $srcSkillsRoot -DestinationDirectory $rooSkillsRoot -Label "Roo (.roo\\skills)"
}

function Sync-SkillsToGitHub {
    param(
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    $srcSkillsRoot = Join-Path $RepoRoot ".ai\skills"
    $githubSkillsRoot = Join-Path $RepoRoot ".github\skills"

    Invoke-RoboCopyMirror -SourceDirectory $srcSkillsRoot -DestinationDirectory $githubSkillsRoot -Label "GitHub (.github\\skills)"
}

function Sync-SkillsToClaude {
    param(
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    $srcSkillsRoot = Join-Path $RepoRoot ".ai\skills"
    $claudeSkillsRoot = Join-Path $RepoRoot ".claude\skills"

    Invoke-RoboCopyMirror -SourceDirectory $srcSkillsRoot -DestinationDirectory $claudeSkillsRoot -Label "Claude Code (.claude\\skills)"
}

# --- Main Script ---
if (-not $NoClear) {
    Clear-Host
}

# We are located under `.ai/skills/<skill>/tools`. Find repo root by going up 4 levels.
$scriptDir = $PSScriptRoot
$repoRoot = (Join-Path -Path $scriptDir -ChildPath "..\..\..\.." | Resolve-Path).Path

# `.ai` folder path
$aiDir = Join-Path $repoRoot ".ai"

# Discover source files matching *instructions.md in the .ai folder
[System.IO.FileSystemInfo[]]$sourceInstructionFiles = Get-ChildItem -Path $aiDir -Filter "*instructions.md" -File | Sort-Object Name

if ($null -eq $sourceInstructionFiles -or $sourceInstructionFiles.Length -eq 0) {
    Write-Warning "No '*instructions.md' files found in '$aiDir'. Nothing to process."
    exit 0
}

Write-Host "Found the following source instruction files in '$aiDir':"
$sourceInstructionFiles | ForEach-Object { Write-Host "- $($_.Name)" }

# Mode parameter handling: if 'ALL' or 'AUTO', skip interactive prompt
if ($Mode -eq 'ALL') {
    Write-Host "Selected: ALL (parameter mode)"
    $updateCline = $true
    $updateCopilot = $true
    $updateRooCode = $true
    $updateCodex = $true
    $updateClaude = $true
}
elseif ($Mode -eq 'AUTO') {
    Write-Host "Selected: AUTO (parameter mode)"
    # Determine available agents based on instruction files
    $updateCline = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.clinerules')
    $updateRooCode = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.roo\rules')
    $updateCopilot = Test-Path (Join-Path $repoRoot '.github\copilot-instructions.md') -PathType Leaf
    $updateCodex = Test-Path (Join-Path $repoRoot 'AGENTS.md') -PathType Leaf
    $updateClaude = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.claude')
    Write-Host "Agents to update based on available instruction files:"
    if ($updateCline) { Write-Host "- CLINE" }
    if ($updateRooCode) { Write-Host "- ROO CODE" }
    if ($updateCopilot) { Write-Host "- GitHub CoPilot" }
    if ($updateCodex) { Write-Host "- OpenAI Codex" }
    if ($updateClaude) { Write-Host "- Claude Code" }
}
elseif ($Mode -and $Mode -ne '') {
    # Specific agent mode (e.g., CLINE, "ROO CODE", etc.)
    $updateCline = ($Mode -eq 'CLINE')
    $updateCopilot = ($Mode -eq 'GitHub CoPilot')
    $updateRooCode = ($Mode -eq 'ROO CODE')
    $updateCodex = ($Mode -eq 'OpenAI Codex')
    $updateClaude = ($Mode -eq 'Claude Code')
    Write-Host "Selected: $Mode (parameter mode)"
}
else {
    # User prompt for agent selection
    # Detect available agents for interactive menu
    $hasCline = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.clinerules')
    $hasRooCode = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.roo\rules')
    $hasCopilot = Test-Path (Join-Path $repoRoot '.github\copilot-instructions.md') -PathType Leaf
    $hasCodex = Test-Path (Join-Path $repoRoot 'AGENTS.md') -PathType Leaf
    $hasClaude = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.claude')

    Write-Host "`r`nDetected AI agents with instruction files:"
    if ($hasCline) { Write-Host "- CLINE" }
    if ($hasRooCode) { Write-Host "- ROO CODE" }
    if ($hasCopilot) { Write-Host "- GitHub CoPilot" }
    if ($hasCodex) { Write-Host "- OpenAI Codex" }
    if ($hasClaude) { Write-Host "- Claude Code" }

    Write-Host ""
    Write-Host "=============================================================="
    Write-Host "Select Agent Instruction Set to Update"
    Write-Host "--------------------------------------------------------------"
    Write-Host "1. AUTO           - Update only agents with instruction files (default)"
    Write-Host "2. ALL            - Update instructions for all AI agents"
    Write-Host "3. CLINE          - Update instructions for CLINE"
    Write-Host "4. ROO CODE       - Update instructions for ROO CODE"
    Write-Host "5. GitHub CoPilot - Update instructions for GitHub CoPilot"
    Write-Host "6. OpenAI Codex   - Update instructions for OpenAI Codex"
    Write-Host "7. Claude Code    - Update instructions for Claude Code"
    Write-Host "0. Exit"
    Write-Host "=============================================================="
    $selection = Read-Host "Enter the number of your choice (0-7)"

    # Initialize flags
    $updateCline = $false
    $updateCopilot = $false
    $updateRooCode = $false
    $updateCodex = $false
    $updateClaude = $false

    switch ($selection) {
        '1' {
            $updateCline = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.clinerules')
            $updateRooCode = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.roo\rules')
            $updateCopilot = Test-Path (Join-Path $repoRoot '.github\copilot-instructions.md') -PathType Leaf
            $updateCodex = Test-Path (Join-Path $repoRoot 'AGENTS.md') -PathType Leaf
            $updateClaude = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.claude')
            Write-Host "Selected: AUTO"
        }
        '2' {
            $updateCline = $true
            $updateCopilot = $true
            $updateRooCode = $true
            $updateCodex = $true
            $updateClaude = $true
            Write-Host "Selected: ALL"
        }
        '3' { $updateCline = $true; Write-Host "Selected: CLINE" }
        '4' { $updateRooCode = $true; Write-Host "Selected: ROO CODE" }
        '5' { $updateCopilot = $true; Write-Host "Selected: GitHub CoPilot" }
        '6' { $updateCodex = $true; Write-Host "Selected: OpenAI Codex" }
        '7' { $updateClaude = $true; Write-Host "Selected: Claude Code" }
        '0' { Write-Host "Operation cancelled by user."; exit 0 }
        default { throw "Invalid selection. Exiting." }
    }
}

# --- Multiple-File Agent Updates ---
if ($updateCline) {
    Update-MultipleFileAgent -AgentName "CLINE" -TargetDirectory ".clinerules" -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
}

if ($updateRooCode) {
    Update-MultipleFileAgent -AgentName "ROO CODE" -TargetDirectory ".roo\rules" -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
}

# --- Single-File Agent Updates ---
if ($updateCopilot) {
    $copilotTarget = ".github\copilot-instructions.md"
    $githubInstructionsDir = Join-Path $repoRoot ".github\instructions"

    if (Test-Path $githubInstructionsDir -PathType Container) {
        Write-Host "`r`n--- Updating GitHub CoPilot Instructions (folder-based) ---"

        $mainName = "instructions.md"
        $mainSource = $sourceInstructionFiles | Where-Object { $_.Name -ieq $mainName } | Select-Object -First 1
        if ($null -eq $mainSource) {
            throw "Expected source '$mainName' under .ai but none found."
        }

        Copy-FileIfDifferent -SourcePath $mainSource.FullName -TargetPath (Join-Path $repoRoot $copilotTarget)

        foreach ($sf in $sourceInstructionFiles) {
            if ($sf.Name -ieq $mainName) {
                continue
            }

            $destination = Join-Path $githubInstructionsDir $sf.Name
            Copy-FileIfDifferent -SourcePath $sf.FullName -TargetPath $destination
        }
    }
    else {
        Update-SingleFileAgent -AgentName "GitHub CoPilot" -TargetFilePath $copilotTarget -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
    }
}

if ($updateCodex) {
    Update-SingleFileAgent -AgentName "OpenAI Codex" -TargetFilePath "AGENTS.md" -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
}

# --- Claude Code (multiple-file agent) ---
if ($updateClaude) {
    Update-MultipleFileAgent -AgentName "Claude Code" -TargetDirectory ".claude" -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
}

# --- Skills mirroring ---
if ($updateRooCode -or $Mode -eq 'ALL' -or $Mode -eq 'AUTO') {
    Sync-SkillsToRoo -RepoRoot $repoRoot
}

# GitHub Copilot: mirror skills to `.github/skills` (Copilot tries to load from there).
if ($updateCopilot -or $Mode -eq 'ALL' -or $Mode -eq 'AUTO') {
    Sync-SkillsToGitHub -RepoRoot $repoRoot
}

# Claude Code: mirror skills to `.claude/skills`.
if ($updateClaude -or $Mode -eq 'ALL' -or $Mode -eq 'AUTO') {
    Sync-SkillsToClaude -RepoRoot $repoRoot
}

Write-Host "`r`nAll selected operations completed successfully."

# Only pause when launched by double-click (Explorer). In CI / terminal usage, do not pause.
if ($Host.Name -and $Host.Name -notlike '*ConsoleHost*') {
    Invoke-Pause
}


================================================
FILE: .editorconfig
================================================
root = true

[*]
charset = utf-8
# Line endings: Let Git handle normalization via .gitattributes and core.autocrlf
# - Repository stores LF (normalized by Git)
# - Working tree uses OS-native line endings (CRLF on Windows, LF on Unix)
# - Uncomment below to force editors to use LF (useful for LF-everywhere workflows):
# end_of_line = lf
insert_final_newline = true
trim_trailing_whitespace = true

# Spaces at the end can be meaningful in Markdown (hard line breaks)
[*.md]
trim_trailing_whitespace = false

# Windows PowerShell 5.1 can misinterpret UTF-8 without BOM when non-ASCII exists.
# If you are PowerShell 7+ only, you may prefer charset = utf-8 here.
[*.ps1]
charset = utf-8-bom


================================================
FILE: .github/copilot-instructions.md
================================================
## Role

Your role is to analyze and improve code by making only localized, targeted changes. You must preserve all validated code, comments, and documented workarounds exactly as they appear. Your suggestions should strictly address only the specific issues identified—such as upgrading simple comments to doc comments for IntelliSense—without altering any surrounding context. Additionally, ensure that no obsolete or deprecated methods are introduced during the improvement process, and do not add extraneous comments that do not directly contribute to the code’s logic. Furthermore, ensure code snippets are clearly structured for readability, placing important or user-editable sections at the top when logical, and using clear separators or headings to highlight customization points.
Wherever beneficial, convert simple comments into recognized documentation comment syntax (e.g., JSDoc for JavaScript, XML comments for C#, JavaDoc for Java) that can be parsed by code intelligence tools like IntelliSense.
Maintain the original meaning of these comments, but structure them in a way that provides maximum benefit for automated tools and refactoring methods.
Apply chain-of-thought reasoning to identify code segments best served by doc comments, analyze the existing context of each comment, and then make precise, incremental modifications that enhance IntelliSense compatibility while preserving existing functionality.

## Output

Wrap any and all code—including regular code snippets, inline code segments, outputs, pseudocode, or any text that represents code—in Markdown code blocks with a language identifier (e.g., ```typescript, ```powershell).


================================================
FILE: .github/instructions/coding-guideline.instructions.md
================================================
# Coding Guidelines

- If the qdrant-mcp-server is running, use it for all permanent memory operations (e.g. storing user information).
- After making changes, ALWAYS start a new server for testing.
- Kill all existing related servers from previous testing before starting a new server.
- Prefer the simplest viable solution; avoid over-engineering.
- Do not add broad try/catch or wrapper layers unless required by a failing test or explicit requirement; if you catch, rethrow to preserve the stack.
- Before writing new code, actively look for existing utilities or functions that can be reused instead of duplicated.
- New helper methods or classes must be justified with a clear, documented need for functionality that is unavailable elsewhere in the codebase.
- Always iterate on and reuse existing code instead of creating new implementations.
- Avoid adding layers of abstraction that do not deliver clear value.
- Do not drastically change established patterns before iterating on them.
- No duplication / SSOT: update or move existing code instead of adding parallel implementations. If you introduce a replacement, remove the old one **in the same change**.
- Write code that accounts for different environments (dev, test, and prod).
- Only modify what is explicitly requested or clearly necessary; do **not** create new files or modules unless explicitly requested.
- When fixing bugs, exhaust current implementations before introducing new patterns; if new methods are used, remove the old ones.
- Keep the codebase clean and organized.
- Avoid one-off scripts unless absolutely necessary.
- Use mocks only for tests, not for dev or prod.
- Never add stubbing or fake data in dev or prod environments.
- Never overwrite the .env file without explicit confirmation.
- Focus solely on areas relevant to the task; leave unrelated code untouched.
- Write thorough tests for all major functionality.
- Avoid major changes to the existing architecture unless explicitly instructed.
- Always consider the impact on other methods and areas of the code.
- Prefer to wrap long lines for better readability.
- Preserve existing formatting; limit formatting to lines you changed and match surrounding style. Also remove any unused imports/usings or dead code **introduced by your edits**.
- Stability primitives (repeatability > cleverness): when the repo provides an established way to perform an operation (repo-owned script, documented command snippet, standard PS1 under .ai/Scripts), treat it as the single source of truth. Use it verbatim instead of synthesizing “equivalent” commands. Only deviate when explicitly asked or when the primitive is proven broken in this environment (and then fix the primitive, not invent a parallel path).
- No code file that you **create or modify** may exceed **6000 tokens (~24 KB)** once your changes are applied.
  - If your changes alone would push the file past this limit, either trim the change or ask for explicit permission to refactor; do **not** alter unrelated code solely to meet the limit.
  - Existing oversized files are left untouched unless the user explicitly requests a refactor.

## Source Control Conventions

Naming conventions for issues, branches, and pull requests.

### Categories

| Category | Use for |
|----------|---------|
| `FEAT`   | New features |
| `FIX`    | Bug fixes |
| `TECH`   | Infrastructure, dependencies, refactoring |
| `DOCS`   | Documentation |

### Naming Patterns

| Item       | Pattern | Example |
|------------|---------|---------|
| **Issue**  | `{CATEGORY}: {Description}` | `FEAT: Download logs to CSV` |
| **Branch** | `{CATEGORY}-{issue#}-{lowercase-dashed-name}` | `FEAT-21-download-logs-to-csv` |
| **PR**     | `PR: #{issue#}: {CATEGORY}: {Description}` | `PR: #21: FEAT: Download logs to CSV` |

- Branch names: lowercase, words separated by dashes, non-ASCII replaced with a single dash, derived from issue title but may be shortened.
- PR body must reference the issue with `Closes #{issue#}`.
- Merge via PR only — no direct pushes to `main` or `master`.
- Feature branches are always created from `main` or `master`. Never merge one feature branch into another — only merge `main` if you need to catch up.
- Always create branches from latest origin/main or origin/main, never merge sub-branches, confirm before risky git ops.
- Do not add Co-Authored-By {AI model}/{AI company} lines to commits.
- Never close issues before a release is published with the fix.

Use the following guidelines:

1. Doc Comment Enhancement for IntelliSense

    - Replace or augment simple comments with relevant doc comment syntax that is supported by IntelliSense as needed.
    - Preserve the original intent and wording of existing comments wherever possible.

2. Code Layout for Clarity

    - Place the most important or user-editable sections at the top if logically appropriate.
    - Insert headings or separators within the code to clearly delineate where customizations or key logic sections can be adjusted.

3. No Extraneous Code Comments

    - Do not include "one-off" or user-directed commentary in the code.
    - Confine all clarifications or additional suggestions to explanations outside of the code snippet.

4. Avoid Outdated or Deprecated Methods

    - Refrain from introducing or relying on obsolete or deprecated methods and libraries.
    - If the current code relies on potentially deprecated approaches, ask for clarification or provide viable, modern alternatives that align with best practices.

5. Testing and Validation

    - Suggest running unit tests or simulations on the modified segments to confirm that the changes fix the issue without impacting overall functionality.
    - Ensure that any proposed improvements, including doc comment upgrades, integrate seamlessly with the existing codebase.
    - After all code modifications, navigate to the affected project directory and build C# then Angular to confirm the application compiles without errors:
		cd {PROJECT} && dotnet build {PROJECT}.csproj
		cd {PROJECT}/ClientApp && ng build
    - Run relevant unit tests if code changes affect core logic.
    - If the developer certificate is not trusted, then execute: dotnet dev-certs https --trust
    - To launch project use: dotnet watch run --project {PROJECT}/{PROJECT}.csproj --launch-profile "{PROJECT} (NG Build)"

6. Rationale and Explanation

    - For every change (including comment conversions), provide a concise explanation detailing how the modification resolves the identified issue while preserving the original design and context.
    - Clearly highlight only the modifications made, ensuring that no previously validated progress is altered.
    - NOTE: Summarize reasoning for the user, but do NOT expose full chain-of-thought. Keep internal deliberations internal; surface only the concise rationale needed to justify each change.

7. Contextual Analysis

    - Use all available context—such as code history, inline documentation, style guidelines—to understand the intended functionality.
    - When inspecting an existing file for understanding, prefer reading the whole file in a
      single `read_file` call when it comfortably fits in context; switch to targeted slices
      only when the file is too large, the tool truncates it, or a specific anchor line is
      already known.
    - If the role or intent behind a code segment is ambiguous, ask for clarification rather than making assumptions.

8. Targeted, Incremental Changes

    - Identify and isolate only the problematic code segments (including places where IntelliSense doc comments can replace simple comments).
    - Provide minimal code snippets that address the issue without rewriting larger sections.
    - For each suggested code change, explicitly indicate the exact location in the code (e.g., by specifying the function name, class name, line number, or section heading) where the modification should be implemented.

9. Preservation of Context

    - Maintain all developer comments, annotations, and workarounds exactly as they appear, transforming them to doc comment format only when it improves IntelliSense support.
    - Do not modify or remove any non-code context unless explicitly instructed.
    - Avoid introducing new, irrelevant comments in the code.

10. Launching {PROJECT} Correctly:
    - Navigate to the {PROJECT} project folder.
    - Run the following command to launch the project with live reload and proper debugging configuration:
      dotnet watch run --launch-profile "{PROJECT} (NG Build)" --project {PROJECT}/{PROJECT}.csproj
    - This command will start the {PROJECT} project on the designated debugging session URL.
    - Ensure that any previous {PROJECT} instances are terminated before running this command.


================================================
FILE: .github/instructions/repository-analysis.instructions.md
================================================
# Repository Analysis

## 1. Repository Overview

This document provides a factual reference for the Jocys.com FocusLogger repository, aimed at developers and AI coding agents working on the codebase.

**FocusLogger** is a Windows desktop utility that monitors and logs which process or program takes window focus. It targets users (especially gamers and power users) who experience unexpected focus stealing — where a background process briefly grabs foreground focus, interrupting gameplay or work. The tool logs every focus change with timestamps, process details, window class names, and focus-state flags, allowing users to identify the culprit.

- **Repository:** https://github.com/JocysCom/FocusLogger
- **License:** GNU General Public License v3.0
- **Current version:** 1.2.6
- **Target platform:** Windows 10+ with .NET 8.0
- **Primary audiences:** Gamers, power users, IT support personnel diagnosing focus-stealing issues.

## 2. Top-Level Structure

This section maps every top-level directory and file to help navigate the repository quickly.

| Path | Purpose |
|------|---------|
| `FocusLogger/` | Main application project (WPF, .NET 8.0). Contains all app source code, shared library, and resources. |
| `FocusLogger.Tests/` | MSTest test project. Unit tests for CSV export and UI automation tests. |
| `Documents/` | Release engineering: signing scripts, zip packaging scripts, screenshot tooling, and pre-built release files. |
| `Resources/` | Solution-level shared scripts (currently `ZipFiles.ps1` for checksum-aware zip packaging). |
| `.ai/` | AI agent instructions, coding guidelines, repository analysis, and skills. |
| `JocysCom.FocusLogger.slnx` | Solution file (XML-based `.slnx` format) referencing the two projects. |
| `README.md` | Project overview, download link, system requirements, screenshot. |
| `LICENSE` | GPLv3 license text. |
| `SECURITY.md` | Security vulnerability reporting policy (support@jocys.com). |
| `Settings.XamlStyler` | XamlStyler configuration for consistent XAML formatting. |
| `Solution_Cleanup.ps1` | PowerShell script for cleaning build artifacts. |

## 3. Technology Stack & Key Dependencies

This section lists verified technologies and versions drawn from project files.

| Technology | Version / Detail | Evidence |
|------------|-----------------|----------|
| .NET | 8.0 (`net8.0-windows`) | `JocysCom.FocusLogger.csproj` TargetFramework |
| C# | Implicit (SDK default for .NET 8) | SDK-style project |
| WPF | `<UseWPF>true</UseWPF>` | csproj |
| Windows Forms interop | `<UseWindowsForms>true</UseWindowsForms>` | csproj — used for P/Invoke helpers and DPI awareness |
| MSTest | v3.x (`MSTest.TestFramework 3.*`, `MSTest.TestAdapter 3.*`) | Test csproj PackageReference |
| Microsoft.NET.Test.Sdk | 17.x | Test csproj PackageReference |
| Windows API (user32.dll) | P/Invoke | `NativeMethods.cs` |
| PowerShell | Scripts for build, sign, zip, cleanup | `Documents/`, `Resources/`, root |
| XamlStyler | Config present | `Settings.XamlStyler` |

**No NuGet package dependencies** in the main application project — all functionality comes from .NET SDK and the embedded `JocysCom.ClassLibrary`.

## 4. Architecture & Runtime Model

This section describes how the application is structured and how it operates at runtime.

FocusLogger is a **single-executable WPF desktop application** that polls Windows API functions to detect focus changes. It does not persist log data between sessions (in-memory only) but provides CSV export for offline analysis.

### Architectural layers

```mermaid
graph TD
    subgraph UI["UI Layer (WPF)"]
        App["App.xaml.cs<br/>Entry point, DPI aware"]
        MW["MainWindow.xaml.cs<br/>Main window frame"]
        DLC["DataListControl.xaml.cs<br/>Core logging UI + logic"]
    end

    subgraph Core["Core Logic"]
        DI["DataItem.cs<br/>Log entry model"]
        DIT["DataItemType.cs<br/>Entry type enum"]
        NM["NativeMethods.cs<br/>P/Invoke declarations"]
        CSV["CSV Export<br/>BuildCsvContent, CsvEscape"]
    end

    subgraph Shared["JocysCom.ClassLibrary (embedded)"]
        Config["Configuration<br/>SettingsData, SettingsItem, AssemblyInfo"]
        CompModel["ComponentModel<br/>SortableBindingList, BindingListInvoked"]
        Controls["Controls<br/>ControlsHelper, ItemFormattingConverter,<br/>InfoControl, MessageBoxWindow"]
        Other["Collections, IO, Text, Runtime, Data"]
    end

    subgraph WinAPI["Windows OS"]
        User32["user32.dll"]
    end

    App --> MW --> DLC
    DLC --> DI
    DLC --> NM
    DLC --> CSV
    NM --> User32
    DI --> Config
    DLC --> CompModel
    DLC --> Controls
    MW --> Controls
```

### Key architectural decisions

- **Polling via timer:** A `System.Timers.Timer` with 1ms interval (non-auto-reset) continuously polls `GetActiveWindow()` and `GetForegroundWindow()`. Duplicate events are suppressed via `DataItem.IsSame()`.
- **Thread safety:** Timer fires on a thread-pool thread; UI updates are marshalled via `ControlsHelper.BeginInvoke()`. A `lock(AddLock)` synchronizes the polling logic.
- **Embedded shared library:** `JocysCom.ClassLibrary` files are included directly in `FocusLogger/JocysCom/` rather than as a compiled DLL or NuGet package.
- **No MVVM framework:** Code-behind pattern with data binding. `DataListControl.xaml.cs` contains both view-model-like logic and model interaction.

## 5. Project Inventory

This section lists each project in the solution with its key metadata.

### 5.1 JocysCom.FocusLogger (main application)

| Property | Value |
|----------|-------|
| Path | `FocusLogger/JocysCom.FocusLogger.csproj` |
| Output type | `WinExe` |
| Target framework | `net8.0-windows` |
| Assembly name | `JocysCom.FocusLogger` |
| Description | Find out which process or program is taking the window focus. In game, mouse and keyboard could temporarily stop responding if another program takes the focus. This tool could help diagnose which program is stealing the focus. |
| Version | 1.2.6 |
| NuGet dependencies | None |
| Embedded resources | `Resources/BuildDate.txt` (auto-generated), `Resources/AiAnalysisPrompt.md` |

**Source structure:**

| Directory | Contents |
|-----------|----------|
| `FocusLogger/` (root) | `App.xaml(.cs)`, `MainWindow.xaml(.cs)`, `AssemblyInfo.cs`, `App.ico` |
| `FocusLogger/Common/` | `DataItem.cs`, `DataItemType.cs`, `NativeMethods.cs` |
| `FocusLogger/Controls/` | `DataListControl.xaml(.cs)` — core logging control |
| `FocusLogger/JocysCom/` | Embedded `JocysCom.ClassLibrary` (~30 files across Collections, Common, ComponentModel, Configuration, Controls, Data, IO, Runtime, Text) |
| `FocusLogger/Resources/` | `AiAnalysisPrompt.md`, `BuildDate.txt`, `Icons/` (SVG sources, XAML icons, conversion scripts) |
| `FocusLogger/Properties/` | Publish profiles |

### 5.2 JocysCom.FocusLogger.Tests (test project)

| Property | Value |
|----------|-------|
| Path | `FocusLogger.Tests/JocysCom.FocusLogger.Tests.csproj` |
| Target framework | `net8.0-windows` |
| Test framework | MSTest v3.x |
| Project reference | `FocusLogger/JocysCom.FocusLogger.csproj` |

**Test files:**

| File | Purpose |
|------|---------|
| `CsvExportTests.cs` | Unit tests for `CsvEscape` and `BuildCsvContent` methods |
| `UIAutomationTests.cs` | UI automation tests using `System.Windows.Automation` — launches the built app and interacts with controls by AutomationId |

Run tests with: `dotnet test FocusLogger.Tests/JocysCom.FocusLogger.Tests.csproj`

## 6. Dependency & Data Flow

This section explains how the projects and components relate to each other and how data moves through the system.

### Project dependency graph

```mermaid
graph LR
    Tests["FocusLogger.Tests<br/>(MSTest v3)"] -->|ProjectReference| App["JocysCom.FocusLogger<br/>(WPF App)"]
    App -->|embedded source| Shared["JocysCom.ClassLibrary<br/>(in FocusLogger/JocysCom/)"]
    App -->|P/Invoke| WinAPI["user32.dll"]
```

### Runtime data flow

1. `System.Timers.Timer` fires (1ms interval, non-auto-reset).
2. `DataListControl.UpdateInfo()` acquires `AddLock`.
3. Calls `NativeMethods.GetActiveWindow()` and `NativeMethods.GetForegroundWindow()`.
4. For each handle, `GetItemFromHandle()` creates a `DataItem` with timestamp, focus flags (mouse/keyboard/caret), window title, and window class name.
5. `IsSame()` checks if the event differs from the previous one; if not, it is skipped.
6. `UpdateFromProcess()` enriches the `DataItem` with process name and path (with error handling for restricted processes).
7. The item is inserted at position 0 of `SortableBindingList<DataItem>` via `ControlsHelper.BeginInvoke()` (UI thread dispatch).
8. The WPF `DataGrid` updates via data binding. `ItemFormattingConverter` translates boolean flags to icons.

### CSV export flow

1. User clicks "Save CSV" button.
2. `SaveFileDialog` prompts for file location.
3. `BuildCsvContent()` iterates all `DataItem` entries, writing CSV with headers: Date, PID, Process Name, Active, Mouse, Keyboard, Caret, Window Title, Window Class, Path.
4. File is written as UTF-8.
5. "Explore" button opens the saved file location in Explorer.
6. "AI Prompt Example" button shows the embedded `AiAnalysisPrompt.md` in a `MessageBoxWindow` for users to copy and paste into an AI assistant along with their CSV.

## 7. Build, Test, CI/CD & Operational Workflows

This section documents how the project is built, tested, and released based on repository evidence.

### Build

```bash
dotnet build JocysCom.FocusLogger.slnx
```

- **Pre-build event:** Generates `Resources/BuildDate.txt` with the current ISO 8601 timestamp via PowerShell.
- **Output:** Single `JocysCom.FocusLogger.exe` in `bin/{Configuration}/net8.0-windows/`.
- **Debug configuration:** Embedded PDB symbols (`DebugType: embedded`).

### Test

```bash
dotnet test FocusLogger.Tests/JocysCom.FocusLogger.Tests.csproj
```

- **Framework:** MSTest v3.x with Microsoft.NET.Test.Sdk 17.x.
- **Unit tests:** `CsvExportTests` — validates CSV escaping and content generation.
- **UI automation tests:** `UIAutomationTests` — launches the built application and interacts via `System.Windows.Automation`. Requires a prior build of the main project.

### Release / packaging scripts

| Script | Purpose |
|--------|---------|
| `Documents/App_1_Sign.ps1` | Code-signs the application executable. |
| `Documents/App_2_Zip.ps1` | Packages the signed executable into a release ZIP. |
| `Resources/ZipFiles.ps1` | Shared utility for checksum-aware ZIP creation (compares source/dest checksums before rebuilding). |
| `Documents/Take_Screenshot.ps1` | Captures application screenshot for documentation. |
| `Documents/Take_Screenshot.ps1.cs` | C# helper compiled by the screenshot script. |
| `Solution_Cleanup.ps1` | Cleans `bin/`, `obj/`, and other build artifacts. |

### Icon workflow

SVG icon sources are stored in `FocusLogger/Resources/Icons/Icons_Default/`. The script `Convert_SVG_to_XAML.ps1` converts them to XAML resource dictionaries (`Icons_Default.xaml`).

### CI/CD

No CI/CD workflow files were found under `.github/workflows/`. Builds and releases appear to be performed locally.

## 8. Documentation Map

This section identifies where documentation lives in the repository.

| Location | Audience | Content |
|----------|----------|---------|
| `README.md` | End users, contributors | Project overview, download link, system requirements, screenshot |
| `SECURITY.md` | Security researchers | Vulnerability reporting policy |
| `LICENSE` | All | GPLv3 full text |
| `.ai/ReadMe.md` | AI agents, developers | Explains the purpose of each file in the `.ai/` directory and how custom instructions work for Copilot, CLINE, and Codex |
| `.ai/instructions.md` | AI agents | Role definition and output formatting rules for AI-assisted edits |
| `.ai/coding-guideline.instructions.md` | AI agents | Detailed coding guidelines, source control conventions (branch/PR naming), testing workflow, and constraints for AI agents |
| `.ai/repository-analysis.instructions.md` | AI agents, developers | This file — comprehensive repository reference |
| `.ai/skills/` | AI agents | Skill definitions (e.g., `ai-self-improvement`) for agent-assisted workflows |
| `FocusLogger/Resources/AiAnalysisPrompt.md` | End users | Prompt template for users to paste into AI assistants alongside exported CSV logs |
| `Documents/Images/` | README, users | Application screenshot |
| `Settings.XamlStyler` | Developers | XamlStyler formatting configuration |

### Documentation taxonomy

```mermaid
graph TD
    subgraph EndUsers["End-User Documentation"]
        README["README.md<br/>Overview, download, requirements"]
        SECURITY["SECURITY.md<br/>Vulnerability reporting"]
        LICENSE["LICENSE<br/>GPLv3"]
        AiPrompt["FocusLogger/Resources/<br/>AiAnalysisPrompt.md<br/>Prompt template for CSV analysis"]
        Screenshot["Documents/Images/<br/>Application screenshot"]
    end

    subgraph AIAgents["AI Agent Instructions"]
        AiReadMe[".ai/ReadMe.md<br/>Directory guide"]
        AiInstr[".ai/instructions.md<br/>Role & output rules"]
        AiCoding[".ai/coding-guideline<br/>.instructions.md<br/>Coding & SCM conventions"]
        AiRepo[".ai/repository-analysis<br/>.instructions.md<br/>This file"]
        AiSkills[".ai/skills/<br/>Agent skill definitions"]
    end

    subgraph DevConfig["Developer Configuration"]
        XamlStyler["Settings.XamlStyler<br/>XAML formatting"]
    end
```

## 9. AI-Agent-Relevant Conventions and Constraints

This section captures rules and patterns that materially affect automated edits. The full set of coding and source-control conventions is defined in `.ai/coding-guideline.instructions.md`; the highlights below are the items most likely to cause mistakes if overlooked.

1. **Coding style:** Follow Microsoft C# conventions. PascalCase for public members, camelCase for locals. Some private fields use `_PascalCase` (e.g., `_Date`). Preserve existing naming patterns in each file. Prefer the simplest viable solution; avoid over-engineering.

2. **Doc comments:** Per `.ai/instructions.md`, convert simple comments to XML documentation comments where beneficial for IntelliSense. Do not alter surrounding code when doing so.

3. **Shared library files (`FocusLogger/JocysCom/`):** These are embedded from a shared `JocysCom.ClassLibrary`. Exercise caution when editing — changes here may diverge from the upstream library.

4. **XAML formatting:** The repository uses XamlStyler (see `Settings.XamlStyler`). XAML edits should conform to the configured style.

5. **No NuGet packages in the main app:** All dependencies are framework-provided or embedded source. Do not introduce NuGet package dependencies without explicit approval.

6. **Test project uses MSTest v3:** New tests should follow MSTest v3 patterns (`[TestClass]`, `[TestMethod]`, `Assert.*`).

7. **UI automation tests depend on a built executable:** `UIAutomationTests` locate the app at a relative path from the test output. Building the main project before running these tests is required.

8. **Pre-build event:** The csproj generates `Resources/BuildDate.txt` via PowerShell. This file should not be manually edited or committed.

9. **Solution format:** Uses `.slnx` (XML-based solution format), not the older `.sln` text format.

10. **No CI/CD pipelines:** All build and release steps are manual/local. Scripts in `Documents/` handle signing and packaging.

11. **File size limit:** No code file that is created or modified may exceed 6000 tokens (~24 KB).

12. **Source control conventions:** Issues use `{CATEGORY}: {Description}` (FEAT, FIX, TECH, DOCS). Branches use `{CATEGORY}-{issue#}-{lowercase-dashed-name}`. PRs use `PR: #{issue#}: {CATEGORY}: {Description}` and must reference the issue with `Closes #{issue#}`. Merge via PR only — no direct pushes to `main`.

13. **No Co-Authored-By lines:** Do not add `Co-Authored-By` AI model/company lines to commits.

14. **Issue closure:** Never close issues before a release is published with the fix.

15. **No duplication / SSOT:** Update or move existing code instead of adding parallel implementations. If introducing a replacement, remove the old one in the same change.

16. **Stability primitives:** When the repo provides an established script or command, use it verbatim. Only deviate when it is proven broken, and then fix the primitive rather than inventing a parallel path.


================================================
FILE: .github/skills/ai-self-improvement/SKILL.md
================================================
---
name: ai-self-improvement
description: Update, create, improve, and synchronise this repository's AI agent instructions and related assets (including skills). Use when the user asks to create or edit a skill/SKILL.md, modify the agent's own instructions/processes, restructure instruction governance, migrate instruction content into skills, or run/adjust the sync pipeline that publishes `.ai/` sources into agent-specific folders. Load this skill before writing any SKILL.md, .instructions.md, or touching any skills/ folder (.ai/, .claude/, .roo/, .github/). It tells you the correct location (.ai/) and the sync step, so files end up in the right place.
---

# AI Self-Improvement (Instructions + Skills)

## Critical: `.ai/` is the Primary Source for ALL Agents

The `.ai/` folder is the **single source of truth** for all AI agent configurations in this repository. This applies to:

- **CLINE / Roo Code** — synced to `.roo/rules/` and `.roo/skills/`
- **GitHub Copilot** — synced to `.github/copilot-instructions.md`
- **OpenAI Codex / AGENTS.md** — synced to `AGENTS.md` at repo root
- **Claude Code** — synced to `.claude/*.instructions.md` and `.claude/skills/`

**IMPORTANT:** When asked to modify skills, instructions, or perform any AI self-improvement task, you MUST:

1. Locate the source file under `.ai/` (not the agent-specific output)
2. Make changes to the `.ai/` source
3. Run the sync script to propagate changes to all agents

## Path Mapping Reference

When you encounter a path in an agent-specific folder, map it to `.ai/`:

| Agent-Specific Path | Source Path (Edit Here) |
|---------------------|------------------------|
| `.roo/rules/*.md` | `.ai/*.instructions.md` |
| `.roo/skills/<name>/SKILL.md` | `.ai/skills/<name>/SKILL.md` |
| `.github/copilot-instructions.md` | `.ai/instructions.md` (generated) |
| `AGENTS.md` | `.ai/instructions.md` (generated) |
| `.claude/*.instructions.md` | `.ai/*.instructions.md` |
| `.claude/skills/<name>/SKILL.md` | `.ai/skills/<name>/SKILL.md` |

**Example:** If asked to update `.roo/skills/ai-self-improvement/SKILL.md`, you must edit `.ai/skills/ai-self-improvement/SKILL.md` instead.

## Editable instruction files (sources of truth)

You can update your own instruction files under `.ai/`:

- `.ai/instructions.md` — the main system instructions file
- `.ai/*instructions.md` — additional instruction files (auto-included)
- `.ai/*instructions-detail.md` — detailed instruction files (read only when needed)
- `.ai/skills/<name>/SKILL.md` — skill definition files

## Workflow

1. Treat `.ai/` as the **single source of truth** for agent instructions **and skills**.
2. When creating or migrating a skill, create/update it under `.ai/skills/`.
3. Make instruction changes in `.ai/instructions.md` and related `*.instructions.md` / `*.instructions-detail.md` files.
4. Do **not** edit generated outputs directly (they are produced by the sync script):
   - `.roo/rules/`
   - `.roo/skills/`
   - `.github/copilot-instructions.md`
   - `AGENTS.md`
   - `.claude/`
5. **Test changes before syncing** — verify scripts execute correctly and changes work as expected.
6. After testing, run the sync script to apply to all agents.

## Testing Before Sync

Before running the sync script, always verify your changes work correctly:

- **For script changes**: Execute the modified script and verify output is correct
- **For instruction changes**: Review the markdown renders properly and instructions are clear
- **For skill changes**: Test any bundled tools or scripts included in the skill

**Example**: If you modify a PowerShell script in a skill, run it directly from `.ai/skills/<name>/scripts/` to confirm it works before syncing.

## Activation process

After editing instruction files (or master skills), run from repository root:

```powershell
.\.ai\skills\ai-self-improvement\scripts\Sync-AgentAssets.ps1 AUTO
```

This script synchronizes changes from `.ai/` to all agent-specific folders.

## Single source of truth

**Never embed template content in instructions — reference template files instead.**

Example:

- ✅ "Template maintained in `pr/checklist.template.md`"
- ❌ Pasting template content into instructions

## Bundled scripts

- Sync entrypoint (instructions + skills): `.ai/skills/ai-self-improvement/scripts/Sync-AgentAssets.ps1`


================================================
FILE: .github/skills/ai-self-improvement/scripts/Sync-AgentAssets.ps1
================================================
# Script: Sync-AgentAssets.ps1
# Location: .ai/skills/ai-self-improvement/scripts/Sync-AgentAssets.ps1
# Description:
#   Synchronises AI agent instruction files and skills from master sources under `.ai/`.
#   - Instructions: copies `*.instructions.md` from `.ai/` into agent-specific outputs.
#   - Skills: mirrors `.ai/skills/*` into agent skill folders (e.g. `.roo/skills/*`).
#
# Options for Mode:
#   ALL  - update all known agent outputs
#   AUTO - update only agents that exist in this repository (default usage)
#   Or a specific agent name: CLINE, ROO CODE, GitHub CoPilot, OpenAI Codex, Claude Code

param(
    [Parameter(Position = 0)]
    [string]$Mode,

    [switch]$NoClear
)

# Combine remaining args so Windows PowerShell (-File) invocations like:
#   Sync-AgentAssets.ps1 GitHub CoPilot
# work the same as:
#   Sync-AgentAssets.ps1 "GitHub CoPilot"
if ($args.Count -gt 0) {
    $ModeFromArgs = ($args -join ' ')
    if (-not $Mode -or $Mode -eq '') {
        $Mode = $ModeFromArgs
    }
}

# Allow calling via the old filename (if invoked through a copied/renamed script).
# This only affects displayed script name in prompts/logs.
$scriptName = [System.IO.Path]::GetFileName($MyInvocation.MyCommand.Path)

# Strict mode
Set-StrictMode -Version Latest
$ErrorActionPreference = "Stop"

function Ensure-Directory {
    param(
        [Parameter(Mandatory = $true)]
        [string]$Path
    )

    if (-not (Test-Path -Path $Path -PathType Container)) {
        New-Item -ItemType Directory -Force -Path $Path | Out-Null
    }
}

# Function to check if instruction files exist in a directory
function Test-HasInstructionFiles {
    param(
        [Parameter(Mandatory = $true)]
        [string]$Path,
        [string]$Filter = '*instructions.md'
    )

    if (Test-Path $Path -PathType Container) {
        $files = @(Get-ChildItem $Path -Filter $Filter -File -ErrorAction SilentlyContinue)
        return ($files.Length -gt 0)
    }

    return $false
}

# Function to pause at the end (unless -NoWait is specified)
function Invoke-Pause {
    Write-Host "Pausing for 2 seconds..."
    Start-Sleep -Seconds 2
}

function Copy-FileIfDifferent {
    param(
        [Parameter(Mandatory = $true)]
        [string]$SourcePath,
        [Parameter(Mandatory = $true)]
        [string]$TargetPath
    )

    $targetDir = Split-Path -Path $TargetPath -Parent
    Ensure-Directory -Path $targetDir

    if (-not (Test-Path -Path $TargetPath -PathType Leaf)) {
        Copy-Item -LiteralPath $SourcePath -Destination $TargetPath -Force
        $relative = $TargetPath.Substring($repoRoot.Length + 1)
        Write-Host "Created: $relative"
        return
    }

    $srcBytes = [System.IO.File]::ReadAllBytes($SourcePath)
    $dstBytes = [System.IO.File]::ReadAllBytes($TargetPath)

    if ($srcBytes.Length -eq $dstBytes.Length) {
        $same = $true
        for ($i = 0; $i -lt $srcBytes.Length; $i++) {
            if ($srcBytes[$i] -ne $dstBytes[$i]) { $same = $false; break }
        }

        if ($same) {
            $relative = $TargetPath.Substring($repoRoot.Length + 1)
            Write-Host "Up-to-date: $relative"
            return
        }
    }

    Copy-Item -LiteralPath $SourcePath -Destination $TargetPath -Force
    $relative = $TargetPath.Substring($repoRoot.Length + 1)
    Write-Host "Updated: $relative"
}

function Get-TextAuto {
    param(
        [Parameter(Mandatory = $true)]
        [string]$Path
    )

    # .NET StreamReader detects BOM for UTF-8/UTF-16/UTF-32 automatically.
    $sr = New-Object System.IO.StreamReader($Path, $true)
    try {
        return $sr.ReadToEnd()
    }
    finally {
        $sr.Dispose()
    }
}

function Write-Utf8NoBom {
    param(
        [Parameter(Mandatory = $true)]
        [string]$Path,
        [Parameter(Mandatory = $true)]
        [string]$Content
    )

    $dir = Split-Path -Path $Path -Parent
    Ensure-Directory -Path $dir

    $utf8NoBom = New-Object System.Text.UTF8Encoding($false)
    [System.IO.File]::WriteAllText($Path, $Content, $utf8NoBom)
}

function Assert-InstructionSync {
    param(
        [Parameter(Mandatory = $true)]
        [string]$SourceDirectory,
        [Parameter(Mandatory = $true)]
        [string]$TargetDirectory,
        [Parameter(Mandatory = $true)]
        [System.IO.FileSystemInfo[]]$SourceFiles
    )

    $srcDir = Join-Path $repoRoot $SourceDirectory
    $dstDir = Join-Path $repoRoot $TargetDirectory

    foreach ($sourceFile in $SourceFiles) {
        $srcPath = Join-Path $srcDir $sourceFile.Name
        $dstPath = Join-Path $dstDir $sourceFile.Name

        if (-not (Test-Path $dstPath -PathType Leaf)) {
            throw "Binary comparison failed. Destination file missing: $dstPath"
        }

        $srcBytes = [System.IO.File]::ReadAllBytes($srcPath)
        $dstBytes = [System.IO.File]::ReadAllBytes($dstPath)

        if ($srcBytes.Length -ne $dstBytes.Length) {
            throw "Binary comparison failed. Source and target size mismatch in binary: Source: $srcPath Target: $dstPath"
        }

        for ($i = 0; $i -lt $srcBytes.Length; $i++) {
            if ($srcBytes[$i] -ne $dstBytes[$i]) {
                throw "Binary comparison failed. Source and target content mismatch in binary: Source: $srcPath Target: $dstPath"
            }
        }
    }
}

# Function to update agents that use multiple separate instruction files
function Update-MultipleFileAgent {
    param(
        [Parameter(Mandatory = $true)]
        [string]$AgentName,
        [Parameter(Mandatory = $true)]
        [string]$TargetDirectory,
        [Parameter(Mandatory = $true)]
        [System.IO.FileSystemInfo[]]$SourceFiles,
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    Write-Host "`r`n--- Updating $AgentName Instructions ---"
    $targetDir = Join-Path $RepoRoot $TargetDirectory

    foreach ($sourceFile in $SourceFiles) {
        $targetFile = Join-Path $targetDir $sourceFile.Name
        Copy-FileIfDifferent -SourcePath $sourceFile.FullName -TargetPath $targetFile
    }

    Assert-InstructionSync -SourceDirectory ".ai" -TargetDirectory $TargetDirectory -SourceFiles $SourceFiles
}

# Function to update agents that use a single combined instruction file
function Update-SingleFileAgent {
    param(
        [Parameter(Mandatory = $true)]
        [string]$AgentName,
        [Parameter(Mandatory = $true)]
        [string]$TargetFilePath,
        [Parameter(Mandatory = $true)]
        [System.IO.FileSystemInfo[]]$SourceFiles,
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    Write-Host "`r`n--- Updating $AgentName Instructions ---"
    $targetFile = Join-Path $RepoRoot $TargetFilePath
    $relativeTarget = $targetFile.Substring($repoRoot.Length + 1)

    $allInstructionsContent = New-Object System.Text.StringBuilder
    $firstFile = $true

    foreach ($sourceFile in $SourceFiles) {
        $sourceContent = Get-TextAuto -Path $sourceFile.FullName

        if ([string]::IsNullOrWhiteSpace($sourceContent)) {
            Write-Warning "Skipping empty file: $($sourceFile.Name)"
            continue
        }

        if (-not $firstFile) {
            [void]$allInstructionsContent.AppendLine("")
        }

        [void]$allInstructionsContent.AppendLine("==== START OF INSTRUCTIONS FROM: $($sourceFile.Name) ====")
        [void]$allInstructionsContent.AppendLine("")

        [void]$allInstructionsContent.AppendLine("# Instructions from: $($sourceFile.Name)")
        [void]$allInstructionsContent.AppendLine("")

        [void]$allInstructionsContent.AppendLine($sourceContent.Trim())

        [void]$allInstructionsContent.AppendLine("")
        [void]$allInstructionsContent.AppendLine("==== END OF INSTRUCTIONS FROM: $($sourceFile.Name) ====")

        $firstFile = $false
    }

    $finalContent = $allInstructionsContent.ToString()

    $existing = if (Test-Path -Path $targetFile -PathType Leaf) { Get-TextAuto -Path $targetFile } else { $null }
    if ($null -ne $existing -and $existing -eq $finalContent) {
        Write-Host "Up-to-date: $relativeTarget"
        return
    }

    Write-Utf8NoBom -Path $targetFile -Content $finalContent
    Write-Host "Updated: $relativeTarget"
}

function Invoke-RoboCopyMirror {
    param(
        [Parameter(Mandatory = $true)]
        [string]$SourceDirectory,
        [Parameter(Mandatory = $true)]
        [string]$DestinationDirectory,
        [Parameter(Mandatory = $true)]
        [string]$Label
    )

    if (-not (Test-Path $SourceDirectory -PathType Container)) {
        Write-Host "No skills folder found at: $SourceDirectory"
        return
    }

    Ensure-Directory -Path $DestinationDirectory

    Write-Host "`r`n--- Mirroring skills to $Label ---"
    Write-Host "Source:      $SourceDirectory"
    Write-Host "Destination: $DestinationDirectory"

    # /MIR      = mirror (copy + delete removed)
    # /FFT      = tolerate 2s timestamp granularity
    # /R:1 /W:1 = retry quickly
    # /NFL/NDL  = no file/dir listing (keep output compact)
    # /NJH/NJS  = no job header/summary
    # /NP       = no progress
    # /XD       = exclude version control/build dirs
    $excludedDirs = @('.git', '.vs', 'bin', 'obj')

    $args = @(
        $SourceDirectory,
        $DestinationDirectory,
        '/MIR',
        '/FFT',
        '/R:1',
        '/W:1',
        '/NFL',
        '/NDL',
        '/NJH',
        '/NJS',
        '/NP'
    )

    foreach ($d in $excludedDirs) {
        $args += '/XD'
        $args += $d
    }

    $exe = 'robocopy'
    # Do not echo the full robocopy command; it is noisy and can wrap in some terminals.
    Write-Host "robocopy <source> <destination> /MIR /NFL /NDL /NJH /NJS /NP ..."

    & $exe @args | Out-Null
    $exitCode = $LASTEXITCODE

    # Robocopy uses bitmask exit codes.
    # 0-7 are success with various flags; >= 8 indicates failure.
    if ($exitCode -ge 8) {
        throw "Robocopy failed with exit code $exitCode. Command: $cmd"
    }

    # IMPORTANT: robocopy returns 1+ for successful copies.
    # Ensure PowerShell script does not propagate a non-zero exit code for success cases.
    $global:LASTEXITCODE = 0

    Write-Host "Mirrored skills to $Label (robocopy exit code $exitCode)."
}

function Sync-SkillsToRoo {
    param(
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    $srcSkillsRoot = Join-Path $RepoRoot ".ai\skills"
    $rooSkillsRoot = Join-Path $RepoRoot ".roo\skills"

    Invoke-RoboCopyMirror -SourceDirectory $srcSkillsRoot -DestinationDirectory $rooSkillsRoot -Label "Roo (.roo\\skills)"
}

function Sync-SkillsToGitHub {
    param(
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    $srcSkillsRoot = Join-Path $RepoRoot ".ai\skills"
    $githubSkillsRoot = Join-Path $RepoRoot ".github\skills"

    Invoke-RoboCopyMirror -SourceDirectory $srcSkillsRoot -DestinationDirectory $githubSkillsRoot -Label "GitHub (.github\\skills)"
}

function Sync-SkillsToClaude {
    param(
        [Parameter(Mandatory = $true)]
        [string]$RepoRoot
    )

    $srcSkillsRoot = Join-Path $RepoRoot ".ai\skills"
    $claudeSkillsRoot = Join-Path $RepoRoot ".claude\skills"

    Invoke-RoboCopyMirror -SourceDirectory $srcSkillsRoot -DestinationDirectory $claudeSkillsRoot -Label "Claude Code (.claude\\skills)"
}

# --- Main Script ---
if (-not $NoClear) {
    Clear-Host
}

# We are located under `.ai/skills/<skill>/tools`. Find repo root by going up 4 levels.
$scriptDir = $PSScriptRoot
$repoRoot = (Join-Path -Path $scriptDir -ChildPath "..\..\..\.." | Resolve-Path).Path

# `.ai` folder path
$aiDir = Join-Path $repoRoot ".ai"

# Discover source files matching *instructions.md in the .ai folder
[System.IO.FileSystemInfo[]]$sourceInstructionFiles = Get-ChildItem -Path $aiDir -Filter "*instructions.md" -File | Sort-Object Name

if ($null -eq $sourceInstructionFiles -or $sourceInstructionFiles.Length -eq 0) {
    Write-Warning "No '*instructions.md' files found in '$aiDir'. Nothing to process."
    exit 0
}

Write-Host "Found the following source instruction files in '$aiDir':"
$sourceInstructionFiles | ForEach-Object { Write-Host "- $($_.Name)" }

# Mode parameter handling: if 'ALL' or 'AUTO', skip interactive prompt
if ($Mode -eq 'ALL') {
    Write-Host "Selected: ALL (parameter mode)"
    $updateCline = $true
    $updateCopilot = $true
    $updateRooCode = $true
    $updateCodex = $true
    $updateClaude = $true
}
elseif ($Mode -eq 'AUTO') {
    Write-Host "Selected: AUTO (parameter mode)"
    # Determine available agents based on instruction files
    $updateCline = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.clinerules')
    $updateRooCode = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.roo\rules')
    $updateCopilot = Test-Path (Join-Path $repoRoot '.github\copilot-instructions.md') -PathType Leaf
    $updateCodex = Test-Path (Join-Path $repoRoot 'AGENTS.md') -PathType Leaf
    $updateClaude = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.claude')
    Write-Host "Agents to update based on available instruction files:"
    if ($updateCline) { Write-Host "- CLINE" }
    if ($updateRooCode) { Write-Host "- ROO CODE" }
    if ($updateCopilot) { Write-Host "- GitHub CoPilot" }
    if ($updateCodex) { Write-Host "- OpenAI Codex" }
    if ($updateClaude) { Write-Host "- Claude Code" }
}
elseif ($Mode -and $Mode -ne '') {
    # Specific agent mode (e.g., CLINE, "ROO CODE", etc.)
    $updateCline = ($Mode -eq 'CLINE')
    $updateCopilot = ($Mode -eq 'GitHub CoPilot')
    $updateRooCode = ($Mode -eq 'ROO CODE')
    $updateCodex = ($Mode -eq 'OpenAI Codex')
    $updateClaude = ($Mode -eq 'Claude Code')
    Write-Host "Selected: $Mode (parameter mode)"
}
else {
    # User prompt for agent selection
    # Detect available agents for interactive menu
    $hasCline = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.clinerules')
    $hasRooCode = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.roo\rules')
    $hasCopilot = Test-Path (Join-Path $repoRoot '.github\copilot-instructions.md') -PathType Leaf
    $hasCodex = Test-Path (Join-Path $repoRoot 'AGENTS.md') -PathType Leaf
    $hasClaude = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.claude')

    Write-Host "`r`nDetected AI agents with instruction files:"
    if ($hasCline) { Write-Host "- CLINE" }
    if ($hasRooCode) { Write-Host "- ROO CODE" }
    if ($hasCopilot) { Write-Host "- GitHub CoPilot" }
    if ($hasCodex) { Write-Host "- OpenAI Codex" }
    if ($hasClaude) { Write-Host "- Claude Code" }

    Write-Host ""
    Write-Host "=============================================================="
    Write-Host "Select Agent Instruction Set to Update"
    Write-Host "--------------------------------------------------------------"
    Write-Host "1. AUTO           - Update only agents with instruction files (default)"
    Write-Host "2. ALL            - Update instructions for all AI agents"
    Write-Host "3. CLINE          - Update instructions for CLINE"
    Write-Host "4. ROO CODE       - Update instructions for ROO CODE"
    Write-Host "5. GitHub CoPilot - Update instructions for GitHub CoPilot"
    Write-Host "6. OpenAI Codex   - Update instructions for OpenAI Codex"
    Write-Host "7. Claude Code    - Update instructions for Claude Code"
    Write-Host "0. Exit"
    Write-Host "=============================================================="
    $selection = Read-Host "Enter the number of your choice (0-7)"

    # Initialize flags
    $updateCline = $false
    $updateCopilot = $false
    $updateRooCode = $false
    $updateCodex = $false
    $updateClaude = $false

    switch ($selection) {
        '1' {
            $updateCline = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.clinerules')
            $updateRooCode = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.roo\rules')
            $updateCopilot = Test-Path (Join-Path $repoRoot '.github\copilot-instructions.md') -PathType Leaf
            $updateCodex = Test-Path (Join-Path $repoRoot 'AGENTS.md') -PathType Leaf
            $updateClaude = Test-HasInstructionFiles -Path (Join-Path $repoRoot '.claude')
            Write-Host "Selected: AUTO"
        }
        '2' {
            $updateCline = $true
            $updateCopilot = $true
            $updateRooCode = $true
            $updateCodex = $true
            $updateClaude = $true
            Write-Host "Selected: ALL"
        }
        '3' { $updateCline = $true; Write-Host "Selected: CLINE" }
        '4' { $updateRooCode = $true; Write-Host "Selected: ROO CODE" }
        '5' { $updateCopilot = $true; Write-Host "Selected: GitHub CoPilot" }
        '6' { $updateCodex = $true; Write-Host "Selected: OpenAI Codex" }
        '7' { $updateClaude = $true; Write-Host "Selected: Claude Code" }
        '0' { Write-Host "Operation cancelled by user."; exit 0 }
        default { throw "Invalid selection. Exiting." }
    }
}

# --- Multiple-File Agent Updates ---
if ($updateCline) {
    Update-MultipleFileAgent -AgentName "CLINE" -TargetDirectory ".clinerules" -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
}

if ($updateRooCode) {
    Update-MultipleFileAgent -AgentName "ROO CODE" -TargetDirectory ".roo\rules" -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
}

# --- Single-File Agent Updates ---
if ($updateCopilot) {
    $copilotTarget = ".github\copilot-instructions.md"
    $githubInstructionsDir = Join-Path $repoRoot ".github\instructions"

    if (Test-Path $githubInstructionsDir -PathType Container) {
        Write-Host "`r`n--- Updating GitHub CoPilot Instructions (folder-based) ---"

        $mainName = "instructions.md"
        $mainSource = $sourceInstructionFiles | Where-Object { $_.Name -ieq $mainName } | Select-Object -First 1
        if ($null -eq $mainSource) {
            throw "Expected source '$mainName' under .ai but none found."
        }

        Copy-FileIfDifferent -SourcePath $mainSource.FullName -TargetPath (Join-Path $repoRoot $copilotTarget)

        foreach ($sf in $sourceInstructionFiles) {
            if ($sf.Name -ieq $mainName) {
                continue
            }

            $destination = Join-Path $githubInstructionsDir $sf.Name
            Copy-FileIfDifferent -SourcePath $sf.FullName -TargetPath $destination
        }
    }
    else {
        Update-SingleFileAgent -AgentName "GitHub CoPilot" -TargetFilePath $copilotTarget -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
    }
}

if ($updateCodex) {
    Update-SingleFileAgent -AgentName "OpenAI Codex" -TargetFilePath "AGENTS.md" -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
}

# --- Claude Code (multiple-file agent) ---
if ($updateClaude) {
    Update-MultipleFileAgent -AgentName "Claude Code" -TargetDirectory ".claude" -SourceFiles $sourceInstructionFiles -RepoRoot $repoRoot
}

# --- Skills mirroring ---
if ($updateRooCode -or $Mode -eq 'ALL' -or $Mode -eq 'AUTO') {
    Sync-SkillsToRoo -RepoRoot $repoRoot
}

# GitHub Copilot: mirror skills to `.github/skills` (Copilot tries to load from there).
if ($updateCopilot -or $Mode -eq 'ALL' -or $Mode -eq 'AUTO') {
    Sync-SkillsToGitHub -RepoRoot $repoRoot
}

# Claude Code: mirror skills to `.claude/skills`.
if ($updateClaude -or $Mode -eq 'ALL' -or $Mode -eq 'AUTO') {
    Sync-SkillsToClaude -RepoRoot $repoRoot
}

Write-Host "`r`nAll selected operations completed successfully."

# Only pause when launched by double-click (Explorer). In CI / terminal usage, do not pause.
if ($Host.Name -and $Host.Name -notlike '*ConsoleHost*') {
    Invoke-Pause
}


================================================
FILE: .gitignore
================================================
## Ignore Visual Studio temporary files, build results, and
## files generated by popular Visual Studio add-ons.
##
## Get latest from https://github.com/github/gitignore/blob/master/VisualStudio.gitignore

# User-specific files
*.rsuser
*.suo
*.user
*.userosscache
*.sln.docstates

# User-specific files (MonoDevelop/Xamarin Studio)
*.userprefs

# Mono auto generated files
mono_crash.*

# Build results
[Dd]ebug/
[Dd]ebugPublic/
[Rr]elease/
[Rr]eleases/
x64/
x86/
[Aa][Rr][Mm]/
[Aa][Rr][Mm]64/
bld/
[Bb]in/
[Oo]bj/
[Ll]og/
[Ll]ogs/

# Visual Studio 2015/2017 cache/options directory
.vs/
# Uncomment if you have tasks that create the project's static files in wwwroot
#wwwroot/

# Visual Studio 2017 auto generated files
Generated\ Files/

# MSTest test Results
[Tt]est[Rr]esult*/
[Bb]uild[Ll]og.*

# NUnit
*.VisualState.xml
TestResult.xml
nunit-*.xml

# Build Results of an ATL Project
[Dd]ebugPS/
[Rr]eleasePS/
dlldata.c

# Benchmark Results
BenchmarkDotNet.Artifacts/

# .NET Core
project.lock.json
project.fragment.lock.json
artifacts/

# StyleCop
StyleCopReport.xml

# Files built by Visual Studio
*_i.c
*_p.c
*_h.h
*.ilk
*.meta
*.obj
*.iobj
*.pch
*.pdb
*.ipdb
*.pgc
*.pgd
*.rsp
*.sbr
*.tlb
*.tli
*.tlh
*.tmp
*.tmp_proj
*_wpftmp.csproj
*.log
*.vspscc
*.vssscc
.builds
*.pidb
*.svclog
*.scc

# Chutzpah Test files
_Chutzpah*

# Visual C++ cache files
ipch/
*.aps
*.ncb
*.opendb
*.opensdf
*.sdf
*.cachefile
*.VC.db
*.VC.VC.opendb

# Visual Studio profiler
*.psess
*.vsp
*.vspx
*.sap

# Visual Studio Trace Files
*.e2e

# TFS 2012 Local Workspace
$tf/

# Guidance Automation Toolkit
*.gpState

# ReSharper is a .NET coding add-in
_ReSharper*/
*.[Rr]e[Ss]harper
*.DotSettings.user

# TeamCity is a build add-in
_TeamCity*

# DotCover is a Code Coverage Tool
*.dotCover

# AxoCover is a Code Coverage Tool
.axoCover/*
!.axoCover/settings.json

# Visual Studio code coverage results
*.coverage
*.coveragexml

# NCrunch
_NCrunch_*
.*crunch*.local.xml
nCrunchTemp_*

# MightyMoose
*.mm.*
AutoTest.Net/

# Web workbench (sass)
.sass-cache/

# Installshield output folder
[Ee]xpress/

# DocProject is a documentation generator add-in
DocProject/buildhelp/
DocProject/Help/*.HxT
DocProject/Help/*.HxC
DocProject/Help/*.hhc
DocProject/Help/*.hhk
DocProject/Help/*.hhp
DocProject/Help/Html2
DocProject/Help/html

# Click-Once directory
publish/

# Publish Web Output
*.[Pp]ublish.xml
*.azurePubxml
# Note: Comment the next line if you want to checkin your web deploy settings,
# but database connection strings (with potential passwords) will be unencrypted
*.pubxml
*.publishproj

# Microsoft Azure Web App publish settings. Comment the next line if you want to
# checkin your Azure Web App publish settings, but sensitive information contained
# in these scripts will be unencrypted
PublishScripts/

# NuGet Packages
*.nupkg
# NuGet Symbol Packages
*.snupkg
# The packages folder can be ignored because of Package Restore
**/[Pp]ackages/*
# except build/, which is used as an MSBuild target.
!**/[Pp]ackages/build/
# Uncomment if necessary however generally it will be regenerated when needed
#!**/[Pp]ackages/repositories.config
# NuGet v3's project.json files produces more ignorable files
*.nuget.props
*.nuget.targets

# Microsoft Azure Build Output
csx/
*.build.csdef

# Microsoft Azure Emulator
ecf/
rcf/

# Windows Store app package directories and files
AppPackages/
BundleArtifacts/
Package.StoreAssociation.xml
_pkginfo.txt
*.appx
*.appxbundle
*.appxupload

# Visual Studio cache files
# files ending in .cache can be ignored
*.[Cc]ache
# but keep track of directories ending in .cache
!?*.[Cc]ache/

# Others
ClientBin/
~$*
*~
*.dbmdl
*.dbproj.schemaview
*.jfm
*.pfx
*.publishsettings
orleans.codegen.cs

# Including strong name files can present a security risk
# (https://github.com/github/gitignore/pull/2483#issue-259490424)
#*.snk

# Since there are multiple workflows, uncomment next line to ignore bower_components
# (https://github.com/github/gitignore/pull/1529#issuecomment-104372622)
#bower_components/

# RIA/Silverlight projects
Generated_Code/

# Backup & report files from converting an old project file
# to a newer Visual Studio version. Backup files are not needed,
# because we have git ;-)
_UpgradeReport_Files/
Backup*/
UpgradeLog*.XML
UpgradeLog*.htm
ServiceFabricBackup/
*.rptproj.bak

# SQL Server files
*.mdf
*.ldf
*.ndf

# Business Intelligence projects
*.rdl.data
*.bim.layout
*.bim_*.settings
*.rptproj.rsuser
*- [Bb]ackup.rdl
*- [Bb]ackup ([0-9]).rdl
*- [Bb]ackup ([0-9][0-9]).rdl

# Microsoft Fakes
FakesAssemblies/

# GhostDoc plugin setting file
*.GhostDoc.xml

# Node.js Tools for Visual Studio
.ntvs_analysis.dat
node_modules/

# Visual Studio 6 build log
*.plg

# Visual Studio 6 workspace options file
*.opt

# Visual Studio 6 auto-generated workspace file (contains which files were open etc.)
*.vbw

# Visual Studio LightSwitch build output
**/*.HTMLClient/GeneratedArtifacts
**/*.DesktopClient/GeneratedArtifacts
**/*.DesktopClient/ModelManifest.xml
**/*.Server/GeneratedArtifacts
**/*.Server/ModelManifest.xml
_Pvt_Extensions

# Paket dependency manager
.paket/paket.exe
paket-files/

# FAKE - F# Make
.fake/

# CodeRush personal settings
.cr/personal

# Python Tools for Visual Studio (PTVS)
__pycache__/
*.pyc

# Cake - Uncomment if you are using it
# tools/**
# !tools/packages.config

# Tabs Studio
*.tss

# Telerik's JustMock configuration file
*.jmconfig

# BizTalk build output
*.btp.cs
*.btm.cs
*.odx.cs
*.xsd.cs

# OpenCover UI analysis results
OpenCover/

# Azure Stream Analytics local run output
ASALocalRun/

# MSBuild Binary and Structured Log
*.binlog

# NVidia Nsight GPU debugger configuration file
*.nvuser

# MFractors (Xamarin productivity tool) working folder
.mfractor/

# Local History for Visual Studio
.localhistory/

# BeatPulse healthcheck temp database
healthchecksdb

# Backup folder for Package Reference Convert tool in Visual Studio 2017
MigrationBackup/

# Ionide (cross platform F# VS Code tools) working folder
.ionide/
/FocusLogger/Resources/BuildDate.txt
/FocusLogger/Documents/Files
/.claude/settings.local.json
Documents/Files


================================================
FILE: .markdownlint.json
================================================
// https://github.com/DavidAnson/markdownlint
{
    "default": true,
    "MD013": false, // There are lines that are longer than the configured line_length (default: 80 characters).
    "MD033": false, // Raw HTML is used in a markdown document.
    "MD041": false, // The first line in a document is not a top-level heading.
}

================================================
FILE: Documents/App_1_Sign.ps1
================================================
Import-Module "d:\_Backup\Configuration\SSL\Tools\app_signModule.ps1" -Force

[string[]]$appFiles = @(
    "..\FocusLogger\bin\Release\publish\JocysCom.FocusLogger.exe"
)
[string]$appName = "Jocys.com Focus Logger"
[string]$appLink = "https://www.jocys.com"

ProcessFiles $appName $appLink $appFiles
pause


================================================
FILE: Documents/App_2_Zip.ps1
================================================

# Make sure the output directories exist
$filesDir = Join-Path $PSScriptRoot "Files"
$binDir = Join-Path $PSScriptRoot "..\Resources"

$file1="JocysCom.FocusLogger.exe"
if (-not [System.IO.File]::Exists([System.IO.Path]::Combine($filesDir, $file1))){
    [System.IO.File]::Copy([System.IO.Path]::Combine($PSScriptRoot, "..\App\bin\Release\publish\", $file1), [System.IO.Path]::Combine($filesDir, $file1))
}
& "$binDir\ZipFiles.ps1" $filesDir "$filesDir\JocysCom.FocusLogger.zip" $file1 $true



================================================
FILE: Documents/Take_Screenshot.ps1
================================================
# Take_Screenshot.ps1
# Launches FocusLogger, Notepad, and Explorer, switches between them
# to generate focus log entries, then captures a screenshot using PrintWindow.
#
# Usage: Right-click > Run with PowerShell, or run from terminal:
#   powershell -ExecutionPolicy Bypass -File Take_Screenshot.ps1

Add-Type -AssemblyName System.Windows.Forms
Add-Type -AssemblyName System.Drawing

# Load C# helper class (supports re-running in the same session).
$csFilePath = Join-Path (Split-Path -Parent $MyInvocation.MyCommand.Path) "Take_Screenshot.ps1.cs"
$csFileContent = Get-Content -Path $csFilePath -Raw
$fileHash = Get-FileHash -InputStream ([System.IO.MemoryStream]::new([System.Text.Encoding]::UTF8.GetBytes($csFileContent))) -Algorithm SHA256
$className = "TakeScreenshot"
if (-not $script:loadedClasses) { $script:loadedClasses = @{} }
if (-not $script:loadedClasses.ContainsKey($fileHash.Hash)) {
    $className += (Get-Date -Format "yyyyMMddHHmmss")
    $csCode = $csFileContent -replace "TakeScreenshot", $className
    Add-Type -TypeDefinition $csCode -ReferencedAssemblies System.Windows.Forms, System.Drawing
    $script:loadedClasses[$fileHash.Hash] = $className
} else {
    $className = $script:loadedClasses[$fileHash.Hash]
}
$helper = [Type]$className

$scriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path
$screenshotPath = Join-Path $scriptDir "Images\JocysCom.FocusLogger.png"
$tempFile = Join-Path $env:TEMP "My Document.txt"

# Find FocusLogger executable.
$appPath = Join-Path $scriptDir "..\FocusLogger\bin\Debug\net8.0-windows\JocysCom.FocusLogger.exe"
if (-not (Test-Path $appPath)) {
    $appPath = Join-Path $scriptDir "..\FocusLogger\bin\Release\net8.0-windows\JocysCom.FocusLogger.exe"
}
if (-not (Test-Path $appPath)) {
    Write-Error "FocusLogger not found. Build the project first."
    exit 1
}
$appPath = Resolve-Path $appPath

$focusLogger = $null
$notepad = $null
$explorerProc = $null

try {
    # 1. Start FocusLogger (centered).
    Write-Host "1. Starting FocusLogger..."
    $focusLogger = Start-Process -FilePath $appPath -PassThru
    Start-Sleep -Seconds 2
    $focusLogger.Refresh()
    $flHwnd = $focusLogger.MainWindowHandle
    $helper::CenterAndResize($flHwnd, 920, 480)
    Start-Sleep -Milliseconds 500

    # 2. Start Notepad with a document.
    Write-Host "2. Starting Notepad..."
    "Sample document for Focus Logger screenshot." | Out-File -FilePath $tempFile -Encoding UTF8
    $notepadPidsBefore = @(Get-Process -Name "Notepad" -ErrorAction SilentlyContinue | ForEach-Object { $_.Id })
    Start-Process -FilePath "notepad.exe" -ArgumentList "`"$tempFile`""
    Start-Sleep -Seconds 2
    $notepad = Get-Process -Name "Notepad" -ErrorAction SilentlyContinue |
        Where-Object { $notepadPidsBefore -notcontains $_.Id -and $_.MainWindowHandle -ne [IntPtr]::Zero } |
        Select-Object -First 1
    if (-not $notepad) {
        $notepad = Get-Process -Name "Notepad" -ErrorAction SilentlyContinue |
            Where-Object { $_.MainWindowHandle -ne [IntPtr]::Zero } |
            Select-Object -First 1
    }
    $npHwnd = if ($notepad) { $notepad.MainWindowHandle } else { [IntPtr]::Zero }
    if ($npHwnd -ne [IntPtr]::Zero) {
        $helper::CenterAndResize($npHwnd, 1040, 680, -50)
        $helper::SetForegroundWindow($npHwnd) | Out-Null
        Start-Sleep -Milliseconds 500
    }

    # 3. Start Explorer.
    Write-Host "3. Starting Explorer..."
    $explorerHwndsBefore = @(Get-Process explorer -ErrorAction SilentlyContinue |
        Where-Object { $_.MainWindowHandle -ne [IntPtr]::Zero } |
        ForEach-Object { $_.MainWindowHandle })
    Start-Process "explorer.exe" -ArgumentList "C:\Windows"
    Start-Sleep -Seconds 2
    $explorerProc = Get-Process explorer -ErrorAction SilentlyContinue |
        Where-Object { $_.MainWindowHandle -ne [IntPtr]::Zero -and $explorerHwndsBefore -notcontains $_.MainWindowHandle } |
        Select-Object -First 1
    if (-not $explorerProc) {
        $explorerProc = Get-Process explorer -ErrorAction SilentlyContinue |
            Where-Object { $_.MainWindowTitle -match "Windows" -and $_.MainWindowHandle -ne [IntPtr]::Zero } |
            Select-Object -First 1
    }
    $exHwnd = if ($explorerProc) { $explorerProc.MainWindowHandle } else { [IntPtr]::Zero }
    if ($exHwnd -ne [IntPtr]::Zero) {
        $helper::CenterAndResize($exHwnd, 700, 400)
        $helper::SetForegroundWindow($exHwnd) | Out-Null
        Start-Sleep -Milliseconds 500
    }

    # 4. Switch focus between windows to generate log entries.
    Write-Host "4. Switching focus..."
    if ($npHwnd -ne [IntPtr]::Zero) { $helper::SetForegroundWindow($npHwnd) | Out-Null; Start-Sleep -Milliseconds 800 }
    if ($exHwnd -ne [IntPtr]::Zero) { $helper::SetForegroundWindow($exHwnd) | Out-Null; Start-Sleep -Milliseconds 800 }
    if ($npHwnd -ne [IntPtr]::Zero) { $helper::SetForegroundWindow($npHwnd) | Out-Null; Start-Sleep -Milliseconds 800 }
    if ($exHwnd -ne [IntPtr]::Zero) { $helper::SetForegroundWindow($exHwnd) | Out-Null; Start-Sleep -Milliseconds 800 }
    if ($npHwnd -ne [IntPtr]::Zero) { $helper::SetForegroundWindow($npHwnd) | Out-Null; Start-Sleep -Milliseconds 800 }

    # 5. Move Notepad behind FocusLogger as white background, then capture.
    Write-Host "5. Taking screenshot..."
    if ($npHwnd -ne [IntPtr]::Zero) {
        $helper::CenterAndResize($npHwnd, 1040, 680, -50)
        $helper::SetForegroundWindow($npHwnd) | Out-Null
        Start-Sleep -Milliseconds 300
    }
    $helper::SetForegroundWindow($flHwnd) | Out-Null
    Start-Sleep -Seconds 1
    $helper::CaptureWindow($flHwnd, $screenshotPath)
    Write-Host "   Screenshot saved to: $screenshotPath"

} finally {
    Write-Host "6. Cleaning up..."
    if ($notepad -and -not $notepad.HasExited) { $notepad.Kill(); $notepad.WaitForExit(3000) | Out-Null }
    if ($focusLogger -and -not $focusLogger.HasExited) { $focusLogger.Kill(); $focusLogger.WaitForExit(3000) | Out-Null }
    if ($explorerProc -and -not $explorerProc.HasExited) { $explorerProc.CloseMainWindow() | Out-Null }
    Start-Sleep -Milliseconds 500
    Remove-Item $tempFile -ErrorAction SilentlyContinue
    Write-Host "Done."
}


================================================
FILE: Documents/Take_Screenshot.ps1.cs
================================================
using System;
using System.Drawing;
using System.Drawing.Imaging;
using System.Runtime.InteropServices;
using System.Windows.Forms;

public class TakeScreenshot
{
	[DllImport("user32.dll")]
	public static extern bool SetForegroundWindow(IntPtr hWnd);
	[DllImport("user32.dll")]
	public static extern bool ShowWindow(IntPtr hWnd, int nCmdShow);
	[DllImport("user32.dll")]
	public static extern bool SetWindowPos(IntPtr hWnd, IntPtr hWndInsertAfter, int X, int Y, int cx, int cy, uint uFlags);
	[DllImport("user32.dll")]
	public static extern bool GetWindowRect(IntPtr hWnd, out RECT lpRect);
	[DllImport("user32.dll")]
	public static extern bool PrintWindow(IntPtr hWnd, IntPtr hdcBlt, uint nFlags);
	[DllImport("dwmapi.dll")]
	public static extern int DwmGetWindowAttribute(IntPtr hwnd, int dwAttribute, out RECT pvAttribute, int cbAttribute);

	[StructLayout(LayoutKind.Sequential)]
	public struct RECT
	{
		public int Left, Top, Right, Bottom;
	}

	public static RECT GetExtendedFrameBounds(IntPtr hwnd)
	{
		RECT rect;
		DwmGetWindowAttribute(hwnd, 9, out rect, Marshal.SizeOf(typeof(RECT)));
		return rect;
	}

	public static void CenterAndResize(IntPtr hwnd, int w, int h, int yOffset = 0)
	{
		var screen = Screen.PrimaryScreen.WorkingArea;
		int x = (screen.Width - w) / 2 + screen.Left;
		int y = (screen.Height - h) / 2 + screen.Top + yOffset;
		SetWindowPos(hwnd, IntPtr.Zero, x, y, w, h, 0x0040);
	}

	/// <summary>
	/// Captures a window using CopyFromScreen with DWM extended frame bounds
	/// for accurate visible area (excludes invisible shadow border).
	/// </summary>
	public static void CaptureWindow(IntPtr hwnd, string filePath)
	{
		var rect = GetExtendedFrameBounds(hwnd);
		int w = rect.Right - rect.Left;
		int h = rect.Bottom - rect.Top;
		using (var bitmap = new Bitmap(w, h, PixelFormat.Format32bppArgb))
		{
			using (var graphics = Graphics.FromImage(bitmap))
			{
				graphics.CopyFromScreen(rect.Left, rect.Top, 0, 0, new Size(w, h));
			}
			bitmap.Save(filePath, ImageFormat.Png);
		}
	}
}


================================================
FILE: FocusLogger/App.xaml
================================================
<Application
	x:Class="JocysCom.FocusLogger.App"
	xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
	xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
	xmlns:local="clr-namespace:JocysCom.FocusLogger"
	StartupUri="MainWindow.xaml">
	<Application.Resources>
		<ResourceDictionary>
			<ResourceDictionary.MergedDictionaries>
				<ResourceDictionary Source="JocysCom/Controls/Themes/Default.xaml" />
				<ResourceDictionary Source="JocysCom/Controls/Themes/Icons.xaml" />
				<ResourceDictionary Source="Resources/Icons/Icons_Default.xaml" />
			</ResourceDictionary.MergedDictionaries>
		</ResourceDictionary>
	</Application.Resources>
</Application>


================================================
FILE: FocusLogger/App.xaml.cs
================================================
using System;
using System.Windows;

namespace JocysCom.FocusLogger
{

	public partial class App : Application
	{
		public App()
		{
			SetDPIAware();
		}

		internal class NativeMethods
		{
			[System.Runtime.InteropServices.DllImport("user32.dll")]
			internal static extern bool SetProcessDPIAware();
		}

		public static void SetDPIAware()
		{
			// DPI aware property must be set before application window is created.
			if (Environment.OSVersion.Version.Major >= 6)
				NativeMethods.SetProcessDPIAware();
		}

	}
}


================================================
FILE: FocusLogger/AssemblyInfo.cs
================================================
using System.Windows;

[assembly: ThemeInfo(
	ResourceDictionaryLocation.None, //where theme specific resource dictionaries are located
									 //(used if a resource is not found in the page,
									 // or application resource dictionaries)
	ResourceDictionaryLocation.SourceAssembly //where the generic resource dictionary is located
											  //(used if a resource is not found in the page,
											  // app, or any theme specific resource dictionaries)
)]


================================================
FILE: FocusLogger/Common/DataItem.cs
================================================
using JocysCom.ClassLibrary.Configuration;
using System;
using System.ComponentModel;
using System.Runtime.CompilerServices;

namespace JocysCom.FocusLogger
{
	public class DataItem : SettingsItem
	{

		public DateTime Date { get => _Date; set => SetProperty(ref _Date, value); }
		DateTime _Date;

		public int ProcessId { get => _ProcessId; set => SetProperty(ref _ProcessId, value); }
		int _ProcessId;

		public string ProcessName { get => _ProcessName; set => SetProperty(ref _ProcessName, value); }
		string _ProcessName;

		public string ProcessPath { get => _ProcessPath; set => SetProperty(ref _ProcessPath, value); }
		string _ProcessPath;

		public string WindowTitle { get => _WindowTitle; set => SetProperty(ref _WindowTitle, value); }
		string _WindowTitle;

		public string WindowClassName { get => _WindowClassName; set => SetProperty(ref _WindowClassName, value); }
		string _WindowClassName;

		public bool HasMouse { get => _HasMouse; set => SetProperty(ref _HasMouse, value); }
		bool _HasMouse;

		public bool HasKeyboard { get => _HasKeyboard; set => SetProperty(ref _HasKeyboard, value); }
		bool _HasKeyboard;

		public bool HasCaret { get => _HasCaret; set => SetProperty(ref _HasCaret, value); }
		bool _HasCaret;

		public bool IsActive { get => _IsActive; set => SetProperty(ref _IsActive, value); }
		bool _IsActive;

		public bool NonPath { get => _IsError; set => SetProperty(ref _IsError, value); }
		bool _IsError;

		public bool IsSame(DataItem item)
		{
			return
			item.ProcessId == ProcessId &&
			item.HasMouse == HasMouse &&
			item.HasKeyboard == HasKeyboard &&
			item.HasCaret == HasCaret &&
			item.IsActive == IsActive;
		}

		public System.Windows.MessageBoxImage StatusCode { get => _StatusCode; set => SetProperty(ref _StatusCode, value); }
		System.Windows.MessageBoxImage _StatusCode;

	}
}


================================================
FILE: FocusLogger/Common/DataItemType.cs
================================================
namespace JocysCom.FocusLogger
{
	public enum DataItemType
	{
		None = 0,
	}
}


================================================
FILE: FocusLogger/Common/NativeMethods.cs
================================================
using System;
using System.Runtime.InteropServices;
using System.Text;

namespace JocysCom.FocusLogger
{
	internal class NativeMethods
	{
		// https://docs.microsoft.com/en-gb/windows/win32/api/winuser/

		/// <summary>
		/// Get handle to the window with the keyboard focus.
		/// </summary>
		/// <returns>
		/// The return value is the handle to the window with the keyboard focus.
		/// If the calling thread's message queue does not have an associated window with the keyboard focus, the return value is NULL.
		/// </returns>
		[DllImport("user32.dll", CharSet = CharSet.Auto, ExactSpelling = true)]
		internal static extern IntPtr GetFocus();

		/// <summary>
		/// Window which is active.
		/// </summary>
		/// <returns>
		/// The return value is the handle to the active window attached to the calling thread's message queue.
		/// Otherwise, the return value is NULL.
		/// </returns>
		[DllImport("user32.dll", CharSet = CharSet.Auto, ExactSpelling = true)]
		internal static extern IntPtr GetActiveWindow();

		/// <summary>
		/// Get handle to the child window at the top of the Z order.
		/// </summary>
		[DllImport("user32.dll", CharSet = CharSet.Auto, ExactSpelling = true)]
		internal static extern IntPtr GetTopWindow(IntPtr hWnd);

		[DllImport("user32.dll", CharSet = CharSet.Auto, ExactSpelling = true)]
		internal static extern bool IsWindowVisible(IntPtr hWnd);

		[DllImport("user32.dll", CharSet = CharSet.Auto, ExactSpelling = true)]
		internal static extern int GetWindowTextLengthW(IntPtr hWnd);

		/// <summary>
		/// Copies the text of the specified window's title bar (if it has one) into a buffer.
		/// </summary>
		/// <param name="hWnd">A handle to the window or control containing the text.</param>
		/// <param name="lpString">The buffer that will receive the text.</param>
		/// <param name="nMaxCount">The maximum number of characters to copy to the buffer, including the null character.</param>
		/// <returns>If the function succeeds, the return value is the length, in characters, of the copied string, not including the terminating null character.</returns>
		[DllImport("user32.dll", CharSet = CharSet.Unicode, SetLastError = true)]
		static extern int GetWindowText(IntPtr hWnd, StringBuilder lpString, int nMaxCount);

		/// <summary>
		/// A handle to the window that will receive the keyboard input. 
		/// </summary>
		/// <returns>
		/// The return value is a handle to the foreground window.
		/// The foreground window can be NULL in certain circumstances, such as when a window is losing activation.
		/// </returns>
		[DllImport("user32.dll", CharSet = CharSet.Auto, ExactSpelling = true)]
		internal static extern IntPtr GetForegroundWindow();

		/// <summary>
		/// Retrieves the identifier of the thread that created the specified window and,
		/// optionally, the identifier of the process that created the window.
		/// </summary>
		/// <param name="hWnd">A handle to the window.</param>
		/// <param name="lpdwProcessId">A pointer to a variable that receives the process identifier</param>
		/// <returns>Identifier of the thread that created the window.</returns>
		[DllImport("user32.dll", CharSet = CharSet.Auto, SetLastError = true)]
		internal static extern int GetWindowThreadProcessId(IntPtr hWnd, out int lpdwProcessId);

		/// <summary>
		/// Retrieves information about the active window or a specified GUI thread.
		/// </summary>
		/// <param name="idThread">
		/// The identifier for the thread for which information is to be retrieved.
		/// To retrieve this value, use the GetWindowThreadProcessId function.
		/// If this parameter is NULL, the function returns information for the foreground thread.
		/// </param>
		/// <param name="pgui">
		/// A pointer to a GUITHREADINFO structure that receives information describing the thread. 
		/// </param>
		/// <returns>If the function succeeds, the return value is nonzero.</returns>
		[DllImport("user32.dll", CharSet = CharSet.Auto, SetLastError = true)]
		internal static extern bool GetGUIThreadInfo(int idThread, ref GUITHREADINFO pgui);

		[StructLayout(LayoutKind.Sequential)]
		internal struct RECT
		{
			public int iLeft;
			public int iTop;
			public int iRight;
			public int iBottom;
		}

		[Flags]
		internal enum GUI
		{
			/// <summary>The caret's blink state. This bit is set if the caret is visible.</summary>
			GUI_CARETBLINKING = 0x00000001,
			/// <summary>The thread's menu state. This bit is set if the thread is in menu mode.</summary>
			GUI_INMENUMODE = 0x00000004,
			/// <summary>The thread's move state. This bit is set if the thread is in a move or size loop.</summary>
			GUI_INMOVESIZE = 0x00000002,
			/// <summary>The thread's pop-up menu state. This bit is set if the thread has an active pop-up menu.</summary>
			GUI_POPUPMENUMODE = 0x00000010,
			/// <summary>The thread's system menu state. This bit is set if the thread is in a system menu mode.</summary>
			GUI_SYSTEMMENUMODE = 0x00000008,
		}

		[StructLayout(LayoutKind.Sequential)]
		internal struct GUITHREADINFO
		{
			/// <summary>The size of this structure, in bytes.</summary>
			public int cbSize;
			/// <summary>The thread state.</summary>
			public GUI flags;
			/// <summary>A handle to the active window within the thread.</summary>
			public IntPtr hwndActive;
			/// <summary>A handle to the window that has the keyboard focus.</summary>
			public IntPtr hwndFocus;
			/// <summary>A handle to the window that has captured the mouse.</summary>
			public IntPtr hwndCapture;
			/// <summary>A handle to the window that owns any active menus.</summary>
			public IntPtr hwndMenuOwner;
			/// <summary>A handle to the window in a move or size loop.</summary>
			public IntPtr hwndMoveSize;
			/// <summary>A handle to the window that is displaying the caret.</summary>
			public IntPtr hwndCaret;
			/// <summary>The caret's bounding rectangle, in client coordinates, relative to the window specified by the hwndCaret member.</summary>
			public RECT rectCaret;
		}

		internal static GUITHREADINFO? GetInfo(IntPtr hWnd)
		{
			int lpdwProcessId;
			int threadId = GetWindowThreadProcessId(hWnd, out lpdwProcessId);
			var pgui = new GUITHREADINFO();
			pgui.cbSize = Marshal.SizeOf(pgui);
			if (GetGUIThreadInfo(threadId, ref pgui))
				return pgui;
			return null;
		}

		[DllImport("user32.dll", CharSet = CharSet.Unicode, SetLastError = true)]
		static extern int GetClassName(IntPtr hWnd, StringBuilder lpClassName, int nMaxCount);

		internal static string GetWindowClassName(IntPtr hWnd)
		{
			var sb = new StringBuilder(256);
			var length = GetClassName(hWnd, sb, sb.Capacity);
			return length > 0 ? sb.ToString() : "";
		}

		internal static string GetWindowText(IntPtr hWnd)
		{
			int textLength = GetWindowTextLengthW(hWnd);
			var lpString = new StringBuilder(textLength + 1);
			var length = GetWindowText(hWnd, lpString, lpString.Capacity);
			return lpString.ToString();
		}

	}
}


================================================
FILE: FocusLogger/Controls/DataListControl.xaml
================================================
<UserControl
	x:Class=" JocysCom.FocusLogger.Controls.DataListControl"
	xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
	xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
	xmlns:converters="clr-namespace:JocysCom.ClassLibrary.Controls"
	xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
	xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
	x:Name="This"
	HorizontalAlignment="Stretch"
	VerticalAlignment="Stretch"
	d:DesignHeight="270"
	d:DesignWidth="480"
	Loaded="UserControl_Loaded"
	Unloaded="UserControl_Unloaded"
	mc:Ignorable="d">
	<Grid>
		<Grid.ColumnDefinitions>
			<ColumnDefinition Width="*" />
		</Grid.ColumnDefinitions>
		<Grid.RowDefinitions>
			<RowDefinition Height="Auto" />
			<RowDefinition Height="*" />
		</Grid.RowDefinitions>
		<StackPanel
			Grid.Row="0"
			Margin="3,3,0,0"
			HorizontalAlignment="Left"
			Orientation="Horizontal">
			<Button
				Name="SaveCsvButton"
				Margin="2"
				Padding="3,0,3,0"
				AutomationProperties.AutomationId="SaveCsvButton"
				Background="Transparent"
				Click="SaveCsvButton_Click">
				<StackPanel Style="{StaticResource ButtonStackPanel}">
					<ContentControl Content="{StaticResource Icon_Save}" Focusable="False" />
					<Label Content="Save CSV" Style="{StaticResource ButtonLabel}" />
				</StackPanel>
			</Button>
			<Button
				Name="ExploreCsvButton"
				Margin="2"
				Padding="3,0,3,0"
				AutomationProperties.AutomationId="ExploreCsvButton"
				Background="Transparent"
				Click="ExploreCsvButton_Click">
				<StackPanel Style="{StaticResource ButtonStackPanel}">
					<ContentControl Content="{StaticResource Icon_FolderOpen}" Focusable="False" />
					<Label Content="Explore" Style="{StaticResource ButtonLabel}" />
				</StackPanel>
			</Button>
			<Button
				Name="CopyAiPromptButton"
				Margin="2"
				Padding="3,0,3,0"
				AutomationProperties.AutomationId="CopyAiPromptButton"
				Background="Transparent"
				Click="CopyAiPromptButton_Click">
				<StackPanel Style="{StaticResource ButtonStackPanel}">
					<ContentControl Content="{StaticResource Icon_list}" Focusable="False" />
					<Label Content="AI Prompt Example" Style="{StaticResource ButtonLabel}" />
				</StackPanel>
			</Button>
		</StackPanel>
		<ToolBarPanel Grid.Row="0" HorizontalAlignment="Right" Style="{StaticResource MainToolBarPanel}">
			<Button
				Name="ClearButton"
				Margin="2"
				Padding="3,0,3,0"
				AutomationProperties.AutomationId="ClearButton"
				Background="Transparent"
				Click="ClearButton_Click">
				<StackPanel Style="{StaticResource ButtonStackPanel}">
					<ContentControl Content="{StaticResource Icon_Delete}" Focusable="False" />
					<Label Content="Clear" Style="{StaticResource ButtonLabel}" />
				</StackPanel>
			</Button>
		</ToolBarPanel>
		<DataGrid
			x:Name="MainDataGrid"
			Grid.Row="1"
			HorizontalAlignment="Stretch"
			VerticalAlignment="Stretch"
			x:FieldModifier="public"
			AutoGenerateColumns="False"
			AutomationProperties.AutomationId="MainDataGrid"
			Background="{DynamicResource {x:Static SystemColors.WindowBrushKey}}"
			BorderThickness="0"
			IsReadOnly="True"
			ScrollViewer.CanContentScroll="True"
			ScrollViewer.HorizontalScrollBarVisibility="Auto"
			ScrollViewer.VerticalScrollBarVisibility="Auto"
			SelectionMode="Extended">
			<DataGrid.Resources>
				<converters:ItemFormattingConverter x:Key="_MainDataGridFormattingConverter" />
			</DataGrid.Resources>
			<DataGrid.Columns>
				<DataGridTextColumn
					x:Name="DateColumn"
					Width="Auto"
					EditingElementStyle="{StaticResource TextBlockCell}"
					ElementStyle="{StaticResource TextBlockCell}"
					Header="Date">
					<DataGridTextColumn.Binding>
						<MultiBinding Converter="{StaticResource _MainDataGridFormattingConverter}">
							<Binding RelativeSource="{RelativeSource Self}" />
							<Binding RelativeSource="{RelativeSource TemplatedParent}" />
							<Binding Path="Date" />
						</MultiBinding>
					</DataGridTextColumn.Binding>
				</DataGridTextColumn>
				<DataGridTextColumn
					x:Name="ProcessIdColumn"
					Binding="{Binding ProcessId}"
					EditingElementStyle="{StaticResource TextBoxCell}"
					ElementStyle="{StaticResource TextBlockRightCell}"
					Header="PID" />
				<DataGridTextColumn
					x:Name="ProcessNameColumn"
					Binding="{Binding ProcessName}"
					EditingElementStyle="{StaticResource TextBoxCell}"
					ElementStyle="{StaticResource TextBlockCell}"
					Header="Process Name" />
				<DataGridTemplateColumn
					x:Name="IsActiveImageColumn"
					Width="SizeToCells"
					CanUserResize="False"
					IsReadOnly="True">
					<DataGridTemplateColumn.Header>
						<TextBlock HorizontalAlignment="Center" Text="A" ToolTip="Window is Active" />
					</DataGridTemplateColumn.Header>
					<DataGridTemplateColumn.CellTemplate>
						<DataTemplate>
							<ContentControl x:Name="IsActiveIcon" Width="12" Height="12">
								<ContentControl.Content>
									<MultiBinding Converter="{StaticResource _MainDataGridFormattingConverter}">
										<Binding RelativeSource="{RelativeSource Self}" />
										<Binding RelativeSource="{RelativeSource TemplatedParent}" />
										<Binding Path="IsActive" />
									</MultiBinding>
								</ContentControl.Content>
							</ContentControl>
						</DataTemplate>
					</DataGridTemplateColumn.CellTemplate>
				</DataGridTemplateColumn>
				<DataGridTextColumn
					x:Name="IsActiveColumn"
					EditingElementStyle="{StaticResource TextBoxCell}"
					ElementStyle="{StaticResource TextBlockCell}"
					Header="Active"
					Visibility="Collapsed">
					<DataGridTextColumn.Binding>
						<MultiBinding Converter="{StaticResource _MainDataGridFormattingConverter}">
							<Binding RelativeSource="{RelativeSource Self}" />
							<Binding RelativeSource="{RelativeSource TemplatedParent}" />
							<Binding Path="IsActive" />
						</MultiBinding>
					</DataGridTextColumn.Binding>
				</DataGridTextColumn>
				<DataGridTemplateColumn
					x:Name="HasMouseImageColumn"
					Width="SizeToCells"
					CanUserResize="False"
					IsReadOnly="True">
					<DataGridTemplateColumn.Header>
						<TextBlock HorizontalAlignment="Center" Text="M" ToolTip="Window has Mouse" />
					</DataGridTemplateColumn.Header>
					<DataGridTemplateColumn.CellTemplate>
						<DataTemplate>
							<ContentControl x:Name="HasMouseIcon" Width="12" Height="12">
								<ContentControl.Content>
									<MultiBinding Converter="{StaticResource _MainDataGridFormattingConverter}">
										<Binding RelativeSource="{RelativeSource Self}" />
										<Binding RelativeSource="{RelativeSource TemplatedParent}" />
										<Binding Path="HasMouse" />
									</MultiBinding>
								</ContentControl.Content>
							</ContentControl>
						</DataTemplate>
					</DataGridTemplateColumn.CellTemplate>
				</DataGridTemplateColumn>
				<DataGridTextColumn
					x:Name="HasMouseColumn"
					EditingElementStyle="{StaticResource TextBoxCell}"
					ElementStyle="{StaticResource TextBlockCell}"
					Header="Mouse"
					Visibility="Collapsed">
					<DataGridTextColumn.Binding>
						<MultiBinding Converter="{StaticResource _MainDataGridFormattingConverter}">
							<Binding RelativeSource="{RelativeSource Self}" />
							<Binding RelativeSource="{RelativeSource TemplatedParent}" />
							<Binding Path="HasMouse" />
						</MultiBinding>
					</DataGridTextColumn.Binding>
				</DataGridTextColumn>
				<DataGridTemplateColumn
					x:Name="HasKeyboardImageColumn"
					Width="SizeToCells"
					CanUserResize="False"
					IsReadOnly="True">
					<DataGridTemplateColumn.Header>
						<TextBlock Text="K" ToolTip="Window has Keyboard" />
					</DataGridTemplateColumn.Header>
					<DataGridTemplateColumn.CellTemplate>
						<DataTemplate>
							<ContentControl x:Name="HasKeyboardIcon" Width="12" Height="12">
								<ContentControl.Content>
									<MultiBinding Converter="{StaticResource _MainDataGridFormattingConverter}">
										<Binding RelativeSource="{RelativeSource Self}" />
										<Binding RelativeSource="{RelativeSource TemplatedParent}" />
										<Binding Path="HasKeyboard" />
									</MultiBinding>
								</ContentControl.Content>
							</ContentControl>
						</DataTemplate>
					</DataGridTemplateColumn.CellTemplate>
				</DataGridTemplateColumn>
				<DataGridTextColumn
					x:Name="HasKeyboardColumn"
					EditingElementStyle="{StaticResource TextBoxCell}"
					ElementStyle="{StaticResource TextBlockCell}"
					Header="Keyboard"
					Visibility="Collapsed">
					<DataGridTextColumn.Binding>
						<MultiBinding Converter="{StaticResource _MainDataGridFormattingConverter}">
							<Binding RelativeSource="{RelativeSource Self}" />
							<Binding RelativeSource="{RelativeSource TemplatedParent}" />
							<Binding Path="HasKeyboard" />
						</MultiBinding>
					</DataGridTextColumn.Binding>
				</DataGridTextColumn>
				<DataGridTemplateColumn
					x:Name="HasCaretImageColumn"
					Width="SizeToCells"
					CanUserResize="False"
					IsReadOnly="True">
					<DataGridTemplateColumn.Header>
						<TextBlock HorizontalAlignment="Center" Text="C" ToolTip="Window has Caret" />
					</DataGridTemplateColumn.Header>
					<DataGridTemplateColumn.CellTemplate>
						<DataTemplate>
							<ContentControl x:Name="HasCaretIcon" Width="12" Height="12">
								<ContentControl.Content>
									<MultiBinding Converter="{StaticResource _MainDataGridFormattingConverter}">
										<Binding RelativeSource="{RelativeSource Self}" />
										<Binding RelativeSource="{RelativeSource TemplatedParent}" />
										<Binding Path="HasCaret" />
									</MultiBinding>
								</ContentControl.Content>
							</ContentControl>
						</DataTemplate>
					</DataGridTemplateColumn.CellTemplate>
				</DataGridTemplateColumn>

				<DataGridTextColumn
					x:Name="HasCaretColumn"
					EditingElementStyle="{StaticResource TextBoxCell}"
					ElementStyle="{StaticResource TextBlockCell}"
					Header="Caret"
					Visibility="Collapsed">
					<DataGridTextColumn.Binding>
						<MultiBinding Converter="{StaticResource _MainDataGridFormattingConverter}">
							<Binding RelativeSource="{RelativeSource Self}" />
							<Binding RelativeSource="{RelativeSource TemplatedParent}" />
							<Binding Path="HasCaret" />
						</MultiBinding>
					</DataGridTextColumn.Binding>
				</DataGridTextColumn>
				<DataGridTextColumn
					x:Name="WindowTiteColumn"
					Binding="{Binding WindowTitle}"
					EditingElementStyle="{StaticResource TextBoxCell}"
					ElementStyle="{StaticResource TextBlockCell}"
					Header="Window Title" />
				<DataGridTextColumn
					x:Name="ProcessPathColumn"