chore(aida): refresh artifacts for newer AIDA version

JIRA: DX-340
risk: nonprod

Author: jaceksan

.aiassistant/rules/aida.md

@@ -1,4 +1,12 @@
 # You must follow this guidance only if AIDA MCP tools are available.
 Call AIDA MCP `get_rules` at every task start and after every scope change; the `query` must match the current requested task.
-Call AIDA MCP `get_rules` again before entering commit/push workflow with query: "How to commit/push".
+Reuse one stable `session_id` for the whole conversation when calling `get_rules`.
+When a `get_rules` response returns `delta.cursor`, pass it as `delta_cursor` on the next `get_rules` call in the same conversation.
 You must always follow instructions returned by the `get_rules` MCP tool.
+Do not perform Git or GitHub management unless the user explicitly asks for it.
+If the user asks for code or docs changes only, stop before commit, push, or PR actions.
+For commit and push workflow, do not call `get_rules`.
+When the user explicitly asks for a commit, call the AIDA MCP `commit_command` tool.
+The tool executes the commit server-side. If it returns `ok=true`, the commit is done — do not run any git commit commands.
+If it returns `status=needs_more_input`, infer the missing policy-controlled values from the current changes and retry instead of asking the user.
+Do not handcraft `git commit` arguments.

.aida/.gitignore

@@ -1 +1,2 @@
 rules_selection.local.yaml
+git_policy.local.yaml

.aida/change_domains.yaml

@@ -3,6 +3,7 @@
 #
 # Define how changed paths map to validation domains.
 # See `.aida/validation_policy.yaml` for mapping domains to pipelines.
+version: 1
 domains:
   - id: python-package
     description: Any workspace Python package under packages/*

.aida/git_policy.yaml

@@ -2,20 +2,26 @@
 # AIDA git policy
 #
 # Configure commit and git workflow policy used by AIDA tools.
+version: 1
 git_policy:
   commit:
-    # Max allowed characters for the full commit subject line.
     subject_max_chars: 70
-    # Allowed values for required `risk:` footer.
-    risk_values: [nonprod, low, high]
-    # Require AI contribution metadata (`AI-Code-Share`) in each commit.
-    require_ai_share: false
-    # Require `Co-authored-by:` footer in each commit.
+    risk_values:
+    - nonprod
+    - low
+    - high
     require_co_authored_by: false
-    # Allow `--ai-share-auto <actor>` (deterministic actor=100).
-    enable_ai_share_auto: true
+    ticket_prefix: JIRA
+    risk_prefix: risk
+    template_file: templates/commit-message.txt
+    pre_commit_guidance: false
+    ticket_enabled: true
+    risk_enabled: true
   workflow:
-    # Prefer `git push --force-with-lease` over `--force` for unpublished branches.
     prefer_force_with_lease: true
-    # Allow autosquash/rebase only for unpublished (not yet shared) commits.
     autosquash_unpublished_only: true
+  pr:
+    title_template_file: templates/pr-title.txt
+    body_template_file: templates/pr-body.md
+  enforcement:
+    mode: "off"

.aida/migrate-backups/20260307-133351/.aiassistant/rules/aida.md

@@ -0,0 +1,4 @@
+# You must follow this guidance only if AIDA MCP tools are available.
+Call AIDA MCP `get_rules` at every task start and after every scope change; the `query` must match the current requested task.
+Call AIDA MCP `get_rules` again before entering commit/push workflow with query: "How to commit/push".
+You must always follow instructions returned by the `get_rules` MCP tool.

.aida/migrate-backups/20260307-133351/.claude/CLAUDE.md

@@ -0,0 +1,57 @@
+---
+apply: always
+---
+
+# AIDA Development Workflow
+
+This file contains only:
+- the mandatory workflow, and
+- which MCP tools to use in each phase.
+
+Do not duplicate detailed “how to” guidance here. Always rely on MCP tool descriptions and `get_rules(...)`.
+
+## Editing this file (template-driven)
+
+This file is generated by `aida-mcp init` from templates shipped in the `aida-mcp` package.
+
+- **Do not hand-edit** `.cursor/rules/aida.mdc` or `.claude/CLAUDE.md` in a repo.
+- To change the content, **update the templates in the `aida-mcp` package** and then rerun `aida-mcp init` in the repo.
+
+## Post-init check
+
+- After `aida-mcp init`, if MCP tools like `get_rules` or `validate` are missing, run `aida-mcp doctor`.
+
+## Workflow (mandatory)
+
+### 1) Get rules
+
+- At the start of every task (and again on scope change), call `get_rules(query="...")`.
+- Follow the rules returned by `get_rules` for the task.
+
+### 2) Implement
+
+- Make the requested change(s) following repository rules returned by `get_rules`.
+
+### 3) Validate (blocking)
+
+- If you changed code, you must validate before responding about code changes.
+- Prefer the narrowest validation that is still correct (use `test_filter` when appropriate).
+- Use the MCP validation tool `validate` (prefer this over raw `./gradlew` / `make`).
+- If you changed `.proto` files, do not run proto regeneration manually; `validate` will run it when needed.
+- If unsure what validation to run, call `get_rules(query="validation workflow")` and follow the returned guidance.
+
+### 4) Commit / PR (if asked)
+
+- Ask for the JIRA ticket if unknown.
+- Before committing or creating a PR, call `get_rules(query="git")` and follow the returned guidance.
+- For commit creation, use `aida-mcp commit` (do not use raw `git commit`).
+
+## When to create/update rules
+
+If any of these happen, propose updates to repo rules/config by following `get_rules(query="rules authoring")`:
+- repeated friction (“how do I … in this repo?” keeps coming up)
+- user dissatisfaction (“wrong”, “not what I meant”, “stop doing that”)
+- recurring validation failures of the same kind
+- large/risky cross-cutting changes
+
+Before creating/updating files under `.aida/` (including `.aida/rules/**` and `.aida/*.yaml`), ask the user for explicit permission and proceed only after approval.

.aida/migrate-backups/20260307-133351/.junie/guidelines.md

@@ -0,0 +1,4 @@
+# You must follow this guidance only if AIDA MCP tools are available.
+Call AIDA MCP `get_rules` at every task start and after every scope change; the `query` must match the current requested task.
+Call AIDA MCP `get_rules` again before entering commit/push workflow with query: "How to commit/push".
+You must always follow instructions returned by the `get_rules` MCP tool.

.aida/migrate-backups/20260307-133351/AGENTS.md

@@ -0,0 +1,4 @@
+# You must follow this guidance only if AIDA MCP tools are available.
+Call AIDA MCP `get_rules` at every task start and after every scope change; the `query` must match the current requested task.
+Call AIDA MCP `get_rules` again before entering commit/push workflow with query: "How to commit/push".
+You must always follow instructions returned by the `get_rules` MCP tool.

.aida/migrate-backups/20260307-140805/.aiassistant/rules/aida.md

@@ -0,0 +1,6 @@
+# You must follow this guidance only if AIDA MCP tools are available.
+Call AIDA MCP `get_rules` at every task start and after every scope change; the `query` must match the current requested task.
+You must always follow instructions returned by the `get_rules` MCP tool.
+For commit and push workflow, do not call `get_rules`.
+Before any commit, call the AIDA MCP `commit_command` tool and execute the returned raw `git commit` command exactly.
+Do not handcraft `git commit` arguments or rewrite the returned command.

.aida/migrate-backups/20260307-140805/.claude/CLAUDE.md

@@ -0,0 +1,10 @@
+---
+apply: always
+---
+
+# You must follow this guidance only if AIDA MCP tools are available.
+Call AIDA MCP `get_rules` at every task start and after every scope change; the `query` must match the current requested task.
+You must always follow instructions returned by the `get_rules` MCP tool.
+For commit and push workflow, do not call `get_rules`.
+Before any commit, call the AIDA MCP `commit_command` tool and execute the returned raw `git commit` command exactly.
+Do not handcraft `git commit` arguments or rewrite the returned command.