sync model catalogs and forked models source

Author: furedericca-lab

.github/workflows/release.yaml

@@ -16,10 +16,12 @@ jobs:
       - uses: actions/checkout@v4
         with:
           fetch-depth: 0
+          submodules: recursive
       - name: Refresh models catalog
         run: |
-          git fetch --depth 1 https://github.com/router-for-me/models.git main
-          git show FETCH_HEAD:models.json > internal/registry/models/models.json
+          git -C third_party/models fetch --depth 1 origin main
+          git -C third_party/models checkout --detach FETCH_HEAD
+          cp third_party/models/models.json internal/registry/models/models.json
       - run: git fetch --force --tags
       - uses: actions/setup-go@v4
         with:

.gitmodules

@@ -0,0 +1,4 @@
+[submodule "third_party/models"]
+	path = third_party/models
+	url = https://github.com/furedericca-lab/models.git
+	branch = main

docs/iflow-kimi-k2-5/iflow-kimi-k2-5-contract.md

@@ -0,0 +1,73 @@
+## Context
+
+`kimi-k2.5` previously appeared in the repository's iFlow model catalog during the pre-migration static data era, but it is absent from the active network-refreshed catalog in `internal/registry/models/models.json`. The user requested restoring `kimi-k2.5` under `iflow`.
+
+## Findings
+
+- The active runtime catalog source is `internal/registry/models/models.json`.
+- Git history shows `kimi-k2.5` previously existed under iFlow static data.
+- The current catalog still exposes `kimi-k2.5` under the standalone `kimi` provider.
+- The current iFlow thinking applier does not define provider-specific thinking behavior for Kimi models, so restoring the model entry should not claim unsupported thinking semantics.
+
+## Goals / Non-goals
+
+Goals:
+- Restore `kimi-k2.5` to the active `iflow` model catalog.
+- Keep the change minimal and auditable.
+
+Non-goals:
+- Do not change standalone `kimi` provider definitions.
+- Do not introduce new iFlow-specific thinking behavior for Kimi models without protocol evidence.
+- Do not regenerate or refactor the full catalog pipeline.
+
+## Target files / modules
+
+- `internal/registry/models/models.json`
+
+## Constraints
+
+- Keep JSON valid and preserve existing catalog structure.
+- Avoid adding metadata that suggests unsupported runtime behavior.
+- Use a minimal diff consistent with neighboring iFlow model entries.
+
+## Verification plan
+
+- Query the `iflow` model IDs from `internal/registry/models/models.json` and confirm `kimi-k2.5` is present.
+- Run a JSON validity check on `internal/registry/models/models.json`.
+- Run `git diff --check` to catch formatting or whitespace issues.
+
+## Rollback
+
+- Remove the restored `kimi-k2.5` object from the `iflow` array in `internal/registry/models/models.json`.
+
+## Open questions
+
+- Whether iFlow currently supports Kimi-specific thinking controls remains unverified and is intentionally left unchanged in this task.
+
+## Implementation Notes
+
+- Initial implementation restores the iFlow catalog entry only.
+- Follow-up implementation restores iFlow Kimi fallback thinking behavior by:
+  - re-adding `thinking` metadata to `iflow/kimi-k2.5`
+  - routing Kimi model IDs through the iFlow `enable_thinking` fallback branch
+  - adding focused unit coverage for the Kimi fallback applier path
+
+## Execution Status
+
+- Completed: restored `kimi-k2.5` to the active `iflow` catalog in `internal/registry/models/models.json`.
+- Completed: restored iFlow Kimi fallback thinking handling in `internal/thinking/provider/iflow/apply.go`.
+- Completed: added focused Kimi fallback tests in `internal/thinking/provider/iflow/apply_test.go`.
+- Completed: verified repository task docs with the repo-task-driven validation scripts.
+
+## Evidence
+
+- `bash /root/.openclaw/workspace/skills/repo-task-driven/scripts/doc_placeholder_scan.sh /root/work/CLIProxyAPIPlus/docs/iflow-kimi-k2-5`
+- `bash /root/.openclaw/workspace/skills/repo-task-driven/scripts/post_refactor_text_scan.sh /root/work/CLIProxyAPIPlus/docs/iflow-kimi-k2-5 /root/work/CLIProxyAPIPlus/README.md`
+- `jq -e '.iflow | map(.id) | index("kimi-k2.5") != null' /root/work/CLIProxyAPIPlus/internal/registry/models/models.json`
+- `jq -e '.iflow[] | select(.id == "kimi-k2.5") | .thinking.levels | index("high") != null' /root/work/CLIProxyAPIPlus/internal/registry/models/models.json`
+- `jq -e '.' /root/work/CLIProxyAPIPlus/internal/registry/models/models.json`
+- `git -C /root/work/CLIProxyAPIPlus diff --check`
+
+## Verification Gaps
+
+- `go test ./internal/thinking/provider/iflow` is currently blocked in this environment because `/root/work/CLIProxyAPIPlus/go.mod` declares `go 1.26.0`, and the installed Go toolchain rejects that version string during module parsing.

docs/kiro-model-recovery/kiro-model-recovery-contract.md

@@ -0,0 +1,56 @@
+## Context
+
+The user reported that Kiro also had model deletions. Historical review of `GetKiroModels()` in `internal/registry/model_definitions.go` shows the current registry still contains nearly all historical Kiro models, except for one chat-only variant that disappeared during a Kiro refactor.
+
+## Findings
+
+- Kiro models are defined in `internal/registry/model_definitions.go`, not in `internal/registry/models/models.json`.
+- Historical Kiro IDs used both dotted (`4.5`) and normalized dashed (`4-5`) naming forms during refactors.
+- After normalizing away dotted-to-dashed renames, the only clearly missing historical Kiro model is `kiro-claude-opus-4.5-chat`.
+- The model was removed in commit `204bba9d` during a Kiro refactor and was not replaced with an equivalent chat-only variant.
+
+## Goals / Non-goals
+
+Goals:
+- Restore the missing Kiro Claude Opus 4.5 chat-only variant.
+- Use the current normalized ID style to fit the existing registry.
+
+Non-goals:
+- Do not revert Kiro naming normalization from dotted to dashed IDs.
+- Do not change the current Kiro executor behavior or dynamic model conversion logic.
+- Do not add speculative Kiro models without clear historical evidence.
+
+## Target files / modules
+
+- `internal/registry/model_definitions.go`
+
+## Constraints
+
+- Keep the diff minimal and consistent with neighboring Kiro model definitions.
+- Preserve current Kiro naming conventions (`4-5`, `4-6`, etc.).
+
+## Verification plan
+
+- Confirm the restored model ID is present in `GetKiroModels()`.
+- Run a focused text scan for the restored ID.
+- Run `git diff --check`.
+
+## Rollback
+
+- Remove the restored `kiro-claude-opus-4-5-chat` entry from `GetKiroModels()`.
+
+## Open questions
+
+- None for this bounded recovery task.
+
+## Execution Status
+
+- Completed: compared historical and current Kiro model ID sets.
+- Completed: restored `kiro-claude-opus-4-5-chat` in `GetKiroModels()`.
+
+## Evidence
+
+- `awk '/func GetKiroModels\\(\\)/,/^}/' /root/work/CLIProxyAPIPlus/internal/registry/model_definitions.go | rg 'kiro-claude-opus-4-5-chat|kiro-claude-opus-4-5|kiro-claude-opus-4-5-agentic'`
+- `git -C /root/work/CLIProxyAPIPlus diff --check`
+- `bash /root/.openclaw/workspace/skills/repo-task-driven/scripts/doc_placeholder_scan.sh /root/work/CLIProxyAPIPlus/docs/kiro-model-recovery`
+- `bash /root/.openclaw/workspace/skills/repo-task-driven/scripts/post_refactor_text_scan.sh /root/work/CLIProxyAPIPlus/docs/kiro-model-recovery /root/work/CLIProxyAPIPlus/README.md`

docs/models-fork-submodule/models-fork-submodule-contract.md

@@ -0,0 +1,58 @@
+## Context
+
+The release workflow currently refreshes `internal/registry/models/models.json` by fetching from `https://github.com/router-for-me/models.git`. The user requested switching this source to their fork and adding that fork as a git submodule in the repository.
+
+## Findings
+
+- The repository did not previously have a `.gitmodules` file.
+- The release workflow refresh step is defined in `.github/workflows/release.yaml`.
+- A submodule allows the repository to track the fork explicitly and makes the catalog source auditable.
+
+## Goals / Non-goals
+
+Goals:
+- Add the user's forked `models` repository as a submodule.
+- Update the release workflow to source `models.json` from that submodule instead of the upstream `router-for-me/models` repository.
+
+Non-goals:
+- Do not change unrelated CI behavior.
+- Do not rewrite the internal registry format.
+
+## Target files / modules
+
+- `.gitmodules`
+- `third_party/models` (git submodule)
+- `.github/workflows/release.yaml`
+
+## Constraints
+
+- Keep the release workflow behavior minimal and explicit.
+- Use the fork URL provided by the user.
+
+## Verification plan
+
+- Verify `.gitmodules` contains the new fork URL and branch.
+- Verify the release workflow references `third_party/models`.
+- Verify git recognizes the submodule.
+
+## Rollback
+
+- Remove the submodule entry and revert the workflow refresh step to its previous state.
+
+## Open questions
+
+- None for this bounded task.
+
+## Execution Status
+
+- Completed: added `https://github.com/furedericca-lab/models.git` as the `third_party/models` submodule on branch `main`.
+- Completed: updated the release workflow to refresh `internal/registry/models/models.json` from the forked submodule.
+
+## Evidence
+
+- `.gitmodules` contains:
+  - path `third_party/models`
+  - url `https://github.com/furedericca-lab/models.git`
+  - branch `main`
+- `git -C /root/work/CLIProxyAPIPlus submodule status`
+- `.github/workflows/release.yaml` now initializes submodules and copies `third_party/models/models.json`

docs/models-fork-sync/models-fork-sync-contract.md

@@ -0,0 +1,52 @@
+## Context
+
+The user asked to apply the local `iflow/kiro` model changes into the forked models source at `https://github.com/furedericca-lab/models.git`, which is now mounted as the `third_party/models` submodule.
+
+## Findings
+
+- The submodule repository currently contains only `models.json`.
+- `iflow` models are represented in that file and can be synchronized there.
+- `kiro` models are not stored in the submodule; they live in the main repository code at `internal/registry/model_definitions.go`.
+
+## Goals / Non-goals
+
+Goals:
+- Sync the submodule `iflow` catalog to match the current main-repo `iflow` catalog.
+
+Non-goals:
+- Do not invent a `kiro` section inside the submodule when the source repository has no such schema.
+- Do not change unrelated provider catalogs.
+
+## Target files / modules
+
+- `third_party/models/models.json`
+
+## Constraints
+
+- Keep the submodule JSON valid.
+- Preserve the main repo's current `iflow` decisions exactly.
+
+## Verification plan
+
+- Compare the resulting submodule `iflow` IDs against the main repo `iflow` IDs.
+- Validate `third_party/models/models.json` with `jq`.
+- Run `git diff --check`.
+
+## Rollback
+
+- Revert the `third_party/models/models.json` `iflow` array to the previous submodule state.
+
+## Open questions
+
+- None. `kiro` remains a main-repo-only registry concern because the submodule schema does not contain it.
+
+## Execution Status
+
+- Completed: synced the submodule `iflow` catalog to match the main repository `iflow` catalog.
+- Confirmed: `kiro` changes cannot be mirrored into the submodule because the submodule schema only contains `models.json`.
+
+## Evidence
+
+- `jq -e '.' /root/work/CLIProxyAPIPlus/third_party/models/models.json`
+- `diff -u <(jq -r '.iflow[].id' /root/work/CLIProxyAPIPlus/internal/registry/models/models.json) <(jq -r '.iflow[].id' /root/work/CLIProxyAPIPlus/third_party/models/models.json)`
+- `git -C /root/work/CLIProxyAPIPlus diff --check`

internal/registry/model_definitions.go

@@ -607,6 +607,18 @@ func GetKiroModels() []*ModelInfo {
 			MaxCompletionTokens: 64000,
 			Thinking:            &ThinkingSupport{Min: 1024, Max: 32000, ZeroAllowed: true, DynamicAllowed: true},
 		},
+		// --- Chat Variant (No tool calling, for pure conversation) ---
+		{
+			ID:                  "kiro-claude-opus-4-5-chat",
+			Object:              "model",
+			Created:             1732752000,
+			OwnedBy:             "aws",
+			Type:                "kiro",
+			DisplayName:         "Kiro Claude Opus 4.5 (Chat)",
+			Description:         "Claude Opus 4.5 for chat only (no tool calling)",
+			ContextLength:       200000,
+			MaxCompletionTokens: 64000,
+		},
 		// --- 第三方模型 (通过 Kiro 接入) ---
 		{
 			ID:                  "kiro-deepseek-3-2",