5 Commits

Include renames

Author	SHA1	Message	Date
anhtnm1andClaude Opus 5	a53163ebaf	feat(R04): immutable turn snapshot, typed agent events, conversation service ... EPIC R04 (Team Duy) - the turn lifecycle leaves the widget. R04-T01 domain/agents/conversation_execution_request.py Frozen snapshot of one turn, captured on the UI thread at submit time. The job closure used to read widget/workspace state from inside the worker thread, so a turn could run on a mix of submit-time and later state depending on thread timing. R04-T02 domain/agents/agent_event.py 13 frozen event types replacing untyped emit() dicts, with a two-way bridge so existing widgets keep consuming the legacy shape until EPIC R08. Adds TurnCompletedEvent - the end-of-turn signal the engine never had, which is why a cancelled turn and a failed turn look identical to the UI today. R04-T03 application/conversations/conversation_application_service.py Runs a turn from a request and reports typed events. Never raises across the worker boundary; TurnResult.raise_if_failed() preserves the existing exception-based failure path. begin_turn()/execute_turn() expose the live message list for callers that autosave history mid-run. R04-T04 ui/cowork_tab.py::build_job -> snapshot + service. R04-T05 core/task_executors.py::_run_agent -> same service (was a second, slightly different assembly of the same call). Caught while wiring the bridge: the first event vocabulary had no "notice" event, so Agent Security warnings and auto-compaction notices would have been silently swallowed. Added NoticeEvent plus a test that scans the engine sources for emit() tags and fails when one has no typed counterpart. New: tests/integration/ - real offscreen CoworkTab running a scripted turn end to end (7 tests), including a characterisation of the extra provider call Agent Security spends reviewing each request. Suite: 225 passed, 2.74s. check_imports: PASS. All new files < 400 LOC. 2 pre-existing failures remain in test_config_security.py (EPIC R02/Team Nam). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-21 10:32:14 +09:00
anhtnm1andClaude Opus 5	96bec976e7	feat(R03): unify provider catalogue, routing decisions and usage telemetry ... EPIC R03 (Team Duy) - one provider catalogue, one routing flow, one usage seam. R03-T01 tests/contracts/test_providers.py 29 contract tests every provider must satisfy: canonical assistant message, streamed text == returned content, reasoning never joins the answer, parsed tool arguments, ProviderError for every failure. Real adapters exercised offline by stubbing Provider._request. R03-T02 domain/models/provider_descriptor.py infrastructure/providers/provider_registry.py Provider facts declared once (was split across providers/factory.py, DEFAULT_CONFIG and PROVIDER_LABELS). ProviderRegistry.build() also stamps the descriptor id onto the instance, so ollama/github_copilot/codex usage is no longer all attributed to "openai_compat", and never mutates the caller config. R03-T03 application/model_routing/routing_application_service.py Pure-Python routing policy with four modes: Off, Auto, Manual and the new Fallback (switch only AFTER the current model fails). Depends on a RoutingPort protocol; production wires the existing core.routing engine underneath. R03-T04/T05 ui/chat_panel.py, ui/co4e_tab.py, ui/folder_tab.py Three near-identical routing copies (~40 lines each) replaced by a call to ctx.routing_application() plus a confirm callback. Mode vocabulary now lives in one place (normalize_mode/is_valid_mode) instead of four literal tuples. R03-T06 infrastructure/telemetry/usage_sink.py Token usage extracted from both providers into UsageEvent + UsageEventSink. Estimation pinned against core.usage_tracker so no recorded number changes. Also fixes a deadlock introduced while wiring AppContext: routing_application() held _routing_lock and called routing(), which takes the same non-reentrant lock. Suite: 186 passed, 1.22s. check_imports: PASS. All new files < 400 LOC. 2 pre-existing failures remain in test_config_security.py (EPIC R02/Team Nam). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-21 10:22:28 +09:00
anhtnm1andClaude Opus 5	bbc09f628a	feat(R01): architecture foundation, offline fakes and characterization net ... EPIC R01 (Team Duy) - safety net before the parallel refactor starts. R01-T01 docs/architecture/ADR-001-layered-architecture.md 4-tier boundaries, allowed dependency directions, invariants I1-I6 and the strangler-fig migration strategy. R01-T02 tests/fakes/{fake_provider,fake_tool_executor}.py Scripted, offline Provider and extra-tool executor doubles. R01-T03 scripts/check_imports.py AST-based Clean Architecture Guard (CASAN Check 3). Also covers relative imports and function-local imports; ASCII-only output for cp932 consoles. R01-T04 tests/characterization/test_run_cowork.py 13 snapshot tests pinning run_cowork's current observable contract before EPIC R04 moves its orchestration into application/. R01-T05 docs/architecture/dormant-code.md Import-graph scan: 43 unimported modules verified down to 6 genuinely dormant items (~1887 LOC); the rest run via subprocess/CLI entry points. tests/conftest.py binds `cowork_local` to THIS checkout by absolute path - previously sys.path discovery could import a sibling checkout and the suite would silently test the wrong code. Suite: 104 passed, 1.08s (2 pre-existing failures in test_config_security.py remain - config.py still ships a hardcoded default password, EPIC R02/Team Nam). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-21 10:05:50 +09:00
5 people	1419587401	Feature/fsg gamma team ui fix (#3) ... ## Summary What changed and why? ## Change Type - [ ] Cowork feature - [ ] Bug fix - [x] Core AI contribution - [ ] Test / hardening - [ ] Performance - [ ] Documentation ## Related Work Cowork Task: Core Repo: http://34.143.229.138/gitea-admin/fsg-ai-core-assets Core AI Issue: Core Task: Related PR: ## Scope What is intentionally included? What is intentionally NOT included? ## Validation - [ ] Unit tests - [ ] Integration tests - [ ] Manual verification - [ ] Regression check Commands / evidence: ## Security Impact Permission / credential / network / customer data impact: ## Compatibility - [ ] No breaking change - [ ] Breaking change documented ## Reviewer Notes Anything Cowork reviewers should pay attention to. --------- Co-authored-by: Hiep Ha Van <hiephv3@fpt.com> Co-authored-by: Nam Pham Dinh Thanh <nampdt@fpt.com> Co-authored-by: Lam Hoang Van <lamhv7@fpt.com> Co-authored-by: NamPDT <minhanhpkpro@gmail.com> Reviewed-on: #3	2026-08-20 12:12:56 +00:00
thanhnv	414eaddca3	chore(repo): initialize Cowork Local Gitea repository	2026-08-09 20:12:05 +07:00