feat: add file conflict strategy increment

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,10 +1,13 @@
 ## Description
+
 <!-- Describe your changes in detail -->
 
 ## Related Issue(s)
+
 <!-- Please link to the issue(s) here. If an issue is resolved, use syntax like "closes #123" -->
 
 ## Checklist
+
 - [ ] My code follows the style guidelines of this project
 - [ ] I have performed a self-review of my code
 - [ ] I have commented my code, particularly in hard-to-understand areas
@@ -14,11 +17,13 @@
 - [ ] New and existing unit tests pass locally with my changes
 
 ## Credits & Transparency
+
 <!--
 Please ensure proper credit is given to community members.
 If someone suggested this feature/fix in an issue or discussion, did you add a `Co-authored-by:` trailer to your commit message?
 Did you use AI to assist with this PR? If so, please check the box below and add an `AI-Assisted: true` trailer to your commits.
 -->
+
 - [ ] **Community Credit:** I have credited community members who suggested or contributed to this change (e.g. using `Co-authored-by` commit trailers or referencing issues).
 - [ ] **AI Assistance:** I used AI to assist with this pull request (e.g., code generation, tests).
-  - *If yes, briefly describe what parts were AI-assisted to maintain transparency.*
+  - _If yes, briefly describe what parts were AI-assisted to maintain transparency._

.gitignore

@@ -6,9 +6,12 @@ coverage/
 dist/
 dist-examples/
 node_modules/
+scratch/
+work/
 .env
 *.env
 *.bak*
+*.log
 !.vscode/settings.json
 debug.json
 docs/docs/community/CHANGELOG.md

AGENTS.md

@@ -61,6 +61,7 @@ To maintain testability and GAS compatibility, external service interactions are
 The project examples serve multiple purposes and are all generated from a single source of truth: `src/examples/**.ts`. This file defines the example logic, configuration, end-to-end (E2E) tests, and documentation metadata.
 
 When you modify or create an example in `src/examples/**.ts`, the build process (`npm run update:examples`) automatically generates the following artifacts:
+
 1. **End-to-end tests:** Generated into `src/gas/examples/**-test.js` (used for running tests in Google Apps Script).
 2. **Working example code:** The standalone code that has been E2E-tested, generated into `src/gas/examples/**.js`.
 3. **Example JSON config files:** Configuration representations, generated into `src/examples/**.json`.
@@ -147,6 +148,7 @@ BREAKING CHANGE: The config key `markProcessedMode` has been renamed to `markPro
 Every contribution from the community, no matter how small (e.g., an idea, a suggestion, documentation, an issue report, or discussion), must be properly credited. This applies even if the originally suggested implementation is modified or completely re-implemented from scratch by the repository maintainers or an AI agent. Community involvement is highly valued and must be reflected in the commit history and release notes.
 
 **How to credit contributors:**
+
 - Add a `Co-authored-by: Name <email>` trailer to the end of your commit message. If you only know the contributor's GitHub username, you can use `Co-authored-by: Username <Username@users.noreply.github.com>`.
 - If the contribution originated from an issue or discussion, reference it in the commit message body (e.g., `closes #123` or `resolves #123`). This ensures the release process (like release-please) picks it up.
 - Use the all-contributors CLI to add them to the README.md contributors list. You can run npx all-contributors add <username> <contribution> (e.g. bug, ideas, code, doc) to track it.
@@ -156,6 +158,7 @@ Every contribution from the community, no matter how small (e.g., an idea, a sug
 In alignment with the 2026 EU AI Act and security best practices, we disclose AI involvement to ensure accountability and auditability. The human remains responsible for all code changes.
 
 **How to declare AI assistance:**
+
 - Add the `AI-Assisted: true` trailer to the end of your commit message. This trailer is **required** if AI was used for logic or generation.
 - (Optional) Add the `AI-Tool: <tool-name>` trailer (e.g., `Claude-Code`, `Copilot`, `Aider`).
 - (Optional) Add the `AI-Model: <model-version>` trailer (e.g., `claude-3-5-sonnet-20241022`).

docs/docs/examples/features/conflictStrategy.mdx

@@ -0,0 +1,13 @@
+---
+id: conflictStrategy
+title: Conflict Strategy
+description: Test different conflict strategies like increment.
+---
+import RenderExample from "/src/components/RenderExample.tsx"
+import config from '!!raw-loader!../../../../src/examples/features/conflictStrategy.json';
+import script from '!!raw-loader!../../../../src/gas/examples/features/conflictStrategy.js';
+import { info } from "../../../../src/examples/features/conflictStrategy.ts"
+
+
+
+<RenderExample info={info} config={config} script={script} />