| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 6 | 7 | 0% |
| Commands | 0 | 1 | 3 | 0% |
| Section tags | 1 | 4 | 4 | 11% |
What each file covers
Sections
0 shared · 6 only in A · 7 only in B- − Version Update Workflow
- − 0. Write the Change Description FIRST
- − 1. Source Code Version
- − 2. README.md Updates
- − 3. Version Checker JSON
- − Checklist
- + AGENTS.md
- + Shared Project Memory
- + Testing
- + Cloud LLM Model Maintenance
- + Feature Index
- + Security
- + Git
Commands
0 shared · 1 only in A · 3 only in B- − git log --oneline
- + dotnet build .\UGTLive.sln --configuration Release
- + git commit
- + git push
Section tags
1 shared · 4 only in A · 4 only in B- − code-style
- − deployment
- − agent-behaviour
- − docs
- + test
- + security
- + performance
- + do-not
- git-pr
Line diff
SethRobinson/UGTLive · .cursor/rules/versioning-workflow.mdc
@@ −1 @@
1---
2description: Version update workflow - MUST follow when updating version numbers
3globs: []
4alwaysApply: true
5---
6
7# Version Update Workflow
8
9**CRITICAL**: When the user asks to update/change/increment the version, you MUST update ALL THREE files listed below. Do not update just one file.
10
11When updating the version number for UGTLive, you must update **three files**:
12
13## 0. Write the Change Description FIRST
14
15Before updating any files, run `git log --oneline` to review all commits since the last release. Use the commit messages to write a brief, accurate change description. **Do NOT use placeholder text like "[Description of changes]"** — always write the real description based on the commit log.
16
17The description should:
18- Be brief (one line, matching the style of previous History entries in README.md)
19- Highlight the most notable new features, fixes, and improvements
20- Credit contributors/suggesters where commit messages mention them
21- Be used consistently across both the README history entry and the version checker JSON message
22
23## 1. Source Code Version
24**File:** `src/SplashManager.cs`
25
26Update the `CurrentVersion` constant:
27```csharp
28public const double CurrentVersion = X.XX;
29```
30
31## 2. README.md Updates
32**File:** `README.md`
33
34Update TWO locations:
351. **Version badge** (near top of file):
36 ```markdown
37 [](...
38 ```
39
402. **History section** - Add a new entry at the TOP of the History section:
41 ```markdown
42 **VX.XX [Month] [Day], [Year]** - [Brief description of changes from commit log]
43 ```
44
45## 3. Version Checker JSON
46**File:** `media/latest_version_checker.json`
47
48Update:
49- `latest_version` field to the new version number
50- `message` field with the change description (derived from the same commit log summary)
51
52Example:
53```json
54{
55 "name":"Universal Game Translator Live",
56 "latest_version":X.XX,
57 "message":"Download V{VERSION_STRING} now from rtsoft.com?\n\nChanged: [Description from commit log]"
58}
59```
60
61## Checklist
62- [ ] Read `git log --oneline` since the last release to determine changes
63- [ ] Write the change description based on the commit log (no placeholders!)
64- [ ] `src/SplashManager.cs` - Update `CurrentVersion`
65- [ ] `README.md` - Update version badge
66- [ ] `README.md` - Add history entry with date and real description
67- [ ] `media/latest_version_checker.json` - Update version and message
68
SethRobinson/UGTLive · AGENTS.md
@@ +1 @@
1# AGENTS.md
2
3Project operating instructions for AI assistants working in this repository.
4
5## Shared Project Memory
6
7- At the start of each new task or thread involving this repository, read this file before inspecting files, running commands, making a plan, or taking any other project action.
8- Treat follow-up replies in the same continuous task as part of that task. Do not reread this file unless the repository or working directory changes, this file is modified, or its instructions are no longer available in context.
9- Treat this file as the shared project memory for AI assistants.
10- Do not rely on vendor-specific, proprietary, or hidden memory systems for project facts, preferences, or operating instructions. (except to remember to ALWAYS read this file first before doing anything. Remember that.)
11- Update this file with important repo-specific information learned during work, including build commands, test commands, conventions, decisions, pitfalls, and current project preferences.
12- Keep this file accurate and current. Remove or correct stale, misleading, or incorrect information when discovered.
13- If information is temporary or uncertain, label it clearly rather than presenting it as permanent fact.
14
15Scope policy: this file holds cross-cutting rules, workflows, and gotchas that most sessions need, plus a feature index. Keep it around 30 KB. Feature deep-dives live in `docs/<topic>.md`: before working on a feature listed in the index, read its doc; when finishing feature work, update that doc and keep the index entry here to one or two lines (where it lives + the non-obvious constraint). Cross-cutting rules and new gotchas still land here directly. When a change makes anything stale, here or in a linked doc, update it in the same change.
16
17## Testing
18
19- When possible, design automated tests for new features and bug fixes.
20- Run relevant automated tests after finishing changes to guard against regressions.
21- If tests cannot be run or do not exist, state that clearly in the handoff and describe any manual verification performed.
22- Always finish project changes by building the Release configuration: `dotnet build .\UGTLive.sln --configuration Release`.
23- If a running UGTLive process prevents the Release build, capture its executable/command line, stop it, complete the build, and restart it afterward. Do not start UGTLive if it was not running before the build.
24
25Always add automation/test harnesses to test options/buttons/features as needed. Document them.
26
27## Cloud LLM Model Maintenance
28
29- Cloud and CLI model picker presets live in `src/SettingsWindow.xaml`; their fallback/default values live in `src/ConfigManager.cs`, `src/ConfigManager.Translation.cs`, and `src/SettingsWindow.TranslationSettings.cs`.
30- Subscription-backed CLI providers display as `Anthropic Sub`, `OpenAI Sub`, and `Gemini CLI (Enterprise)`, but their stable internal IDs remain `ClaudeCli`, `CodexCli`, and `GeminiCli`; use `ComboBoxItem.Tag` for the internal ID. Google ended personal/free/AI Pro/AI Ultra access through Gemini CLI on June 18, 2026; do not replace it with Antigravity CLI until `agy -p` reliably exposes captured stdout to Windows parent processes (see `docs/settings-connection-tests.md`).
31- Keep provider-specific capability handling in the matching translation service. In particular, Anthropic model generations use different manual/adaptive thinking request shapes.
32- Verify model IDs and request compatibility against current official provider documentation. Verify OpenRouter-prefixed slugs against its `/api/v1/models` catalog before adding presets.
33
34## Feature Index
35
36- Settings API/model/voice tests: see `docs/settings-connection-tests.md`. UI buttons and `--test-settings-connection` must continue to call the shared `SettingsConnectionTester` implementation.
37- OpenAI All In One Snap translation: see `docs/openai-all-in-one.md`. It is a Snap-only, visual-only `gpt-image-2` Image Edits path; Auto and realtime processing must remain on the standard OCR pipeline.
38
39
40## Security
41
42- Never commit sensitive data, including credentials, tokens, passwords, private keys, cookies, customer data, personal data, or machine-specific authentication material.
43- If an AI assistant needs authentication data or other secrets for local work, use `agents_secret.md` for those notes.
44- `agents_secret.md` must stay ignored by git and must not be committed.
45- Do not put secrets in commit messages, logs, issue text, pull request descriptions, generated docs, or other tracked files.
46- Configuration logging must pass key names through `ConfigManager.IsSensitiveConfigKey`; never print raw secret values in startup or harness output.
47- Before committing, review staged changes for accidental secrets.
48
49## Git
50
51- Never add OpenAI/Codex/Claude etc as a co-author on git commits.
52- NEVER `git commit` unless explicitly told to commit.
53- NEVER `git push` unless explicitly told to push. "Commit" means commit
54 locally only; committing is not permission to push.
55
@@ −1 +1 @@
1−---
2−description: Version update workflow - MUST follow when updating version numbers
3−globs: []
4−alwaysApply: true
5−---
1+# AGENTS.md
62
7−# Version Update Workflow
3+Project operating instructions for AI assistants working in this repository.
84
9−**CRITICAL**: When the user asks to update/change/increment the version, you MUST update ALL THREE files listed below. Do not update just one file.
5+## Shared Project Memory
106
11−When updating the version number for UGTLive, you must update **three files**:
7+- At the start of each new task or thread involving this repository, read this file before inspecting files, running commands, making a plan, or taking any other project action.
8+- Treat follow-up replies in the same continuous task as part of that task. Do not reread this file unless the repository or working directory changes, this file is modified, or its instructions are no longer available in context.
9+- Treat this file as the shared project memory for AI assistants.
10+- Do not rely on vendor-specific, proprietary, or hidden memory systems for project facts, preferences, or operating instructions. (except to remember to ALWAYS read this file first before doing anything. Remember that.)
11+- Update this file with important repo-specific information learned during work, including build commands, test commands, conventions, decisions, pitfalls, and current project preferences.
12+- Keep this file accurate and current. Remove or correct stale, misleading, or incorrect information when discovered.
13+- If information is temporary or uncertain, label it clearly rather than presenting it as permanent fact.
1214
13−## 0. Write the Change Description FIRST
15+Scope policy: this file holds cross-cutting rules, workflows, and gotchas that most sessions need, plus a feature index. Keep it around 30 KB. Feature deep-dives live in `docs/<topic>.md`: before working on a feature listed in the index, read its doc; when finishing feature work, update that doc and keep the index entry here to one or two lines (where it lives + the non-obvious constraint). Cross-cutting rules and new gotchas still land here directly. When a change makes anything stale, here or in a linked doc, update it in the same change.
1416
15−Before updating any files, run `git log --oneline` to review all commits since the last release. Use the commit messages to write a brief, accurate change description. **Do NOT use placeholder text like "[Description of changes]"** — always write the real description based on the commit log.
17+## Testing
1618
17−The description should:
18−- Be brief (one line, matching the style of previous History entries in README.md)
19−- Highlight the most notable new features, fixes, and improvements
20−- Credit contributors/suggesters where commit messages mention them
21−- Be used consistently across both the README history entry and the version checker JSON message
19+- When possible, design automated tests for new features and bug fixes.
20+- Run relevant automated tests after finishing changes to guard against regressions.
21+- If tests cannot be run or do not exist, state that clearly in the handoff and describe any manual verification performed.
22+- Always finish project changes by building the Release configuration: `dotnet build .\UGTLive.sln --configuration Release`.
23+- If a running UGTLive process prevents the Release build, capture its executable/command line, stop it, complete the build, and restart it afterward. Do not start UGTLive if it was not running before the build.
2224
23−## 1. Source Code Version
24−**File:** `src/SplashManager.cs`
25+Always add automation/test harnesses to test options/buttons/features as needed. Document them.
2526
26−Update the `CurrentVersion` constant:
27−```csharp
28−public const double CurrentVersion = X.XX;
29−```
27+## Cloud LLM Model Maintenance
3028
31−## 2. README.md Updates
32−**File:** `README.md`
29+- Cloud and CLI model picker presets live in `src/SettingsWindow.xaml`; their fallback/default values live in `src/ConfigManager.cs`, `src/ConfigManager.Translation.cs`, and `src/SettingsWindow.TranslationSettings.cs`.
30+- Subscription-backed CLI providers display as `Anthropic Sub`, `OpenAI Sub`, and `Gemini CLI (Enterprise)`, but their stable internal IDs remain `ClaudeCli`, `CodexCli`, and `GeminiCli`; use `ComboBoxItem.Tag` for the internal ID. Google ended personal/free/AI Pro/AI Ultra access through Gemini CLI on June 18, 2026; do not replace it with Antigravity CLI until `agy -p` reliably exposes captured stdout to Windows parent processes (see `docs/settings-connection-tests.md`).
31+- Keep provider-specific capability handling in the matching translation service. In particular, Anthropic model generations use different manual/adaptive thinking request shapes.
32+- Verify model IDs and request compatibility against current official provider documentation. Verify OpenRouter-prefixed slugs against its `/api/v1/models` catalog before adding presets.
3333
34−Update TWO locations:
35−1. **Version badge** (near top of file):
36− ```markdown
37− [](...
38− ```
34+## Feature Index
3935
40−2. **History section** - Add a new entry at the TOP of the History section:
41− ```markdown
42− **VX.XX [Month] [Day], [Year]** - [Brief description of changes from commit log]
43− ```
36+- Settings API/model/voice tests: see `docs/settings-connection-tests.md`. UI buttons and `--test-settings-connection` must continue to call the shared `SettingsConnectionTester` implementation.
37+- OpenAI All In One Snap translation: see `docs/openai-all-in-one.md`. It is a Snap-only, visual-only `gpt-image-2` Image Edits path; Auto and realtime processing must remain on the standard OCR pipeline.
4438
45−## 3. Version Checker JSON
46−**File:** `media/latest_version_checker.json`
4739
48−Update:
49−- `latest_version` field to the new version number
50−- `message` field with the change description (derived from the same commit log summary)
40+## Security
5141
52−Example:
53−```json
54−{
55− "name":"Universal Game Translator Live",
56− "latest_version":X.XX,
57− "message":"Download V{VERSION_STRING} now from rtsoft.com?\n\nChanged: [Description from commit log]"
58−}
59−```
42+- Never commit sensitive data, including credentials, tokens, passwords, private keys, cookies, customer data, personal data, or machine-specific authentication material.
43+- If an AI assistant needs authentication data or other secrets for local work, use `agents_secret.md` for those notes.
44+- `agents_secret.md` must stay ignored by git and must not be committed.
45+- Do not put secrets in commit messages, logs, issue text, pull request descriptions, generated docs, or other tracked files.
46+- Configuration logging must pass key names through `ConfigManager.IsSensitiveConfigKey`; never print raw secret values in startup or harness output.
47+- Before committing, review staged changes for accidental secrets.
6048
61−## Checklist
62−- [ ] Read `git log --oneline` since the last release to determine changes
63−- [ ] Write the change description based on the commit log (no placeholders!)
64−- [ ] `src/SplashManager.cs` - Update `CurrentVersion`
65−- [ ] `README.md` - Update version badge
66−- [ ] `README.md` - Add history entry with date and real description
67−- [ ] `media/latest_version_checker.json` - Update version and message
49+## Git
50+
51+- Never add OpenAI/Codex/Claude etc as a co-author on git commits.
52+- NEVER `git commit` unless explicitly told to commit.
53+- NEVER `git push` unless explicitly told to push. "Commit" means commit
54+ locally only; committing is not permission to push.
6855
