chore(conductor): Archive track 'api_metrics_20260223'

This commit is contained in:
2026-02-23 16:53:25 -05:00
parent ad8c0e208b
commit 094e729e89
5 changed files with 54 additions and 5 deletions

View File

@@ -0,0 +1,5 @@
# Track api_metrics_20260223 Context
- [Specification](./spec.md)
- [Implementation Plan](./plan.md)
- [Metadata](./metadata.json)

View File

@@ -0,0 +1,8 @@
{
"track_id": "api_metrics_20260223",
"type": "feature",
"status": "new",
"created_at": "2026-02-23T10:00:00Z",
"updated_at": "2026-02-23T10:00:00Z",
"description": "Review vendor api usage in regards to conservative context handling"
}

View File

@@ -0,0 +1,19 @@
# Implementation Plan
## Phase 1: Metric Extraction and Logic Review [checkpoint: 2668f88]
- [x] Task: Extract explicit cache counts and lifecycle states from Gemini SDK
- [x] Sub-task: Write Tests
- [x] Sub-task: Implement Feature
- [x] Task: Review and expose 'history bleed' (token limit proximity) flags
- [x] Sub-task: Write Tests
- [x] Sub-task: Implement Feature
- [x] Task: Conductor - User Manual Verification 'Phase 1: Metric Extraction and Logic Review' (Protocol in workflow.md)
## Phase 2: GUI Telemetry and Plotting [checkpoint: 76582c8]
- [x] Task: Implement token budget visualizer (e.g., Progress bars for limits) in Dear PyGui
- [x] Sub-task: Write Tests
- [x] Sub-task: Implement Feature
- [x] Task: Implement active caches data display in Provider/Comms panel
- [x] Sub-task: Write Tests
- [x] Sub-task: Implement Feature
- [x] Task: Conductor - User Manual Verification 'Phase 2: GUI Telemetry and Plotting' (Protocol in workflow.md)

View File

@@ -0,0 +1,22 @@
# Specification: Review vendor api usage in regards to conservative context handling
## Overview
This track aims to optimize token efficiency and transparency by reviewing and improving how vendor APIs (Gemini and Anthropic) handle conservative context pruning. The primary focus is on extracting, plotting, and exposing deep metrics to the GUI so developers can intuit how close they are to API limits (e.g., token caps, cache counts, history bleed).
## Scope
- **Gemini Hooks:** Review explicit context caching, cache invalidation, and tools declaration.
- **Global Orchestration:** Review global context boundaries within the main prompt lifecycle.
- **GUI Metrics:** Expose as much metric data as possible to the user interface (e.g., plotting token usage, visual indicators for when "history bleed" occurs, displaying the number of active caches).
## Functional Requirements
- Implement extensive token and cache metric extraction from both Gemini and Anthropic API responses.
- Expose these metrics to the Dear PyGui frontend, potentially utilizing visual plots or progress bars to indicate token budget consumption.
- Implement tests to explicitly verify context rules, ensuring history pruning acts conservatively and predictable without data loss.
## Non-Functional Requirements
- Ensure GUI rendering of new plots or dense metrics does not block the main thread.
- Adhere to the "Strict State Management" product guideline.
## Out of Scope
- Major feature additions unrelated to context token management or telemetry.
- Expanding the AI's agentic capabilities (e.g., new tools).

View File

@@ -7,11 +7,6 @@ This file tracks all major tracks for the project. Each track has its own detail
- [x] **Track: Implement context visualization and memory management improvements** - [x] **Track: Implement context visualization and memory management improvements**
*Link: [./tracks/context_management_20260223/](./tracks/context_management_20260223/)* *Link: [./tracks/context_management_20260223/](./tracks/context_management_20260223/)*
---
- [x] **Track: Review vendor api usage in regards to conservative context handling**
*Link: [./tracks/api_metrics_20260223/](./tracks/api_metrics_20260223/)*