Refactor Gemini model display: filter old versions, group low/high pкo, and improve naming (#114)

* Refactor Gemini model display: filter old versions, group low/high pro, and improve naming * Fix potential negative minutes and refine Gemini 3 Pro grouping logic based on PR feedback * The account change process has been sped up * Address PR review: enhance error message and parameterize polling interval in process handler * Address PR review: fix potential race condition in database backup logic * fix: prevent renderer white screen and harden sentry gating * feat: localize model labels * chore: enable hoisted node-linker * chore: ignore .agent/.claude/.codex in prettier --------- Co-authored-by: Draculabo <[email protected]>
2026-02-19 19:37:30 +08:00
1 parent b9497648c6
commit 8ed4593f73
@@ -19,9 +19,11 @@ Verify that an implementation matches the change artifacts (specs, tasks, design
   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.

 2. **Check status to understand the schema**
+
   ```bash
   openspec status --change "<name>" --json
   ```
+
   Parse the JSON to understand:
   - `schemaName`: The workflow being used (e.g., "spec-driven")
   - Which artifacts exist for this change
@@ -103,6 +105,7 @@ Verify that an implementation matches the change artifacts (specs, tasks, design
 8. **Generate Verification Report**

   **Summary Scorecard**:
+
   ```
   ## Verification Report: <change-name>

@@ -115,7 +118,6 @@ Verify that an implementation matches the change artifacts (specs, tasks, design
   ```

   **Issues by Priority**:
-
   1. **CRITICAL** (Must fix before archive):
      - Incomplete tasks
      - Missing requirement implementations
@@ -154,6 +156,7 @@ Verify that an implementation matches the change artifacts (specs, tasks, design
 **Output Format**

 Use clear markdown with:
+
 - Table for summary scorecard
 - Grouped lists for issues (CRITICAL/WARNING/SUGGESTION)
 - Code references in format: `file.ts:123`