eggg

Prompt

from __future__ import annotations from enum import Enum from typing import Any, Literal from pydantic import BaseModel, Field ChatRole = Literal["system", "user", "assistant", "tool"] class ToolCall(BaseModel): id: str type: str = "function" function_name: str function_arguments: str class ChatMessage(BaseModel): role: str content: str = "" tool_calls: list[dict[str, Any]] | None = None tool_call_id: str | None = None def to_provider_payload(self) -> dict[str, Any]: payload: dict[str, Any] = {"role": self.role, "content": self.content} if self.tool_calls: payload["tool_calls"] = self.tool_calls if self.tool_call_id: payload["tool_call_id"] = self.tool_call_id return payload class ToolStatus(str, Enum): COMPLETED = "completed" ERROR = "error" INTERRUPTED = "interrupted" UNKNOWN = "unknown" class TerminalState(str, Enum): COMPLETED = "completed" FAILED = "failed" CANCELLED = "cancelled" RUNTIME_LIMIT = "runtime_limit" STEP_LIMIT = "step_limit" CONTEXT_LIMIT = "context_limit" class AgentEventType(str, Enum): PROGRESS = "progress" DELTA = "delta" AGENT_EVENT = "agent_event" ERROR = "error" TERMINAL = "terminal" DONE = "done" class AgentEvent(BaseModel): type: str task_id: str step: int = 0 message: str | None = None elapsed_ms: int | None = None content: str | None = None reasoning_content: str | None = None event: dict[str, Any] | None = None code: str | None = None outcome: str | None = None reason: str | None = None tool_calls: int | None = None duration_ms: int | None = None def to_payload(self) -> dict[str, Any]: payload: dict[str, Any] = {"type": self.type, "task_id": self.task_id} if self.step is not None: payload["step"] = self.step if self.message is not None: payload["message"] = self.message if self.elapsed_ms is not None: payload["elapsed_ms"] = self.elapsed_ms if self.content is not None: payload["content"] = self.content if self.reasoning_content is not None: payload["reasoning_content"] = self.reasoning_content if self.event is not None: payload["event"] = self.event if self.code is not None: payload["code"] = self.code if self.outcome is not None: payload["outcome"] = self.outcome if self.reason is not None: payload["reason"] = self.reason if self.tool_calls is not None: payload["tool_calls"] = self.tool_calls if self.duration_ms is not None: payload["duration_ms"] = self.duration_ms return payload class AgentSink: async def send(self, event: AgentEvent) -> None: raise NotImplementedError async def enqueue(self, text: str) -> None: raise NotImplementedError class ToolOutput(BaseModel): status: ToolStatus result: dict[str, Any] = Field(default_factory=dict) class ModelResponse(BaseModel): content: str = "" calls: list[ToolCall] = Field(default_factory=list) finish: str = "" usage: dict[str, Any] | None = None class RuntimeConfig(BaseModel): orca_key: str insta_key: str | None = None browser_hosts: set[str] = Field(default_factory=set) allowed_domains: list[str] = Field(default_factory=list) nixpkgs_rev: str = "" nix_version: str = "" nix_installer_sha256: str = "" deployment_max_request_ms: int = 0 1. [L1 `from __future__ import annotations`] — Ambiguity: In the pasted input this line runs straight on from the prompt text with no line break, so the true first line and file boundary are unclear. 2. [L1 / L21, L22, L62–L71, L117, L122] — Ambiguity: Postponed annotations use PEP 604 `X | None` syntax. The Python and pydantic versions are not pinned. Pydantic must evaluate these strings at class creation, which raises `TypeError` on Python < 3.10 (pydantic v2 without `eval_type_backport`, or pydantic v1). 3. [L8 `ChatRole`] — Broken reference: `ChatRole` is defined but never used anywhere. It is dead code. 4. [L13 `ToolCall.type`] — Type error: Annotated as plain `str` with default `"function"`, so any arbitrary tool-call type string is accepted. 5. [L14–L15 `ToolCall.function_name` / `function_arguments`] — Logic error: The schema is flat, but the provider wire format nests these under `function: {name, arguments}`. No serializer or alias maps between the two shapes. 6. [L15 `ToolCall.function_arguments`] — Type error: Annotated as plain `str`, so JSON validity of the arguments is never checked. 7. [L19 `ChatMessage.role`] — Type error: Annotated as `str` instead of `ChatRole`, so any role string passes validation. 8. [L20 `ChatMessage.content`] — Logic error: The default `""` lets system and user messages with empty content pass validation. 9. [L21 `ChatMessage.tool_calls`] — Type error: Typed as `list[dict[str, Any]]` instead of `list[ToolCall]`. The `ToolCall` model is bypassed, so tool-call structure is unvalidated. 10. [L18–L22 `ChatMessage`] — Logic error: There is no cross-field validation. A `tool` role message can omit `tool_call_id`, and non-assistant roles can carry `tool_calls`. 11. [L25 `to_provider_payload` `"content": self.content`] — Ambiguity: Assistant messages that carry `tool_calls` always send `content: ""` and never `null`. Some providers reject or misinterpret this. 12. [L26 `if self.tool_calls:`] — Logic error: The truthiness check silently drops an explicitly set empty list, so `[]` and `None` become indistinguishable. 13. [L28 `if self.tool_call_id:`] — Logic error: The truthiness check silently drops an empty-string `tool_call_id` instead of surfacing it as invalid. 14. [L33 `ToolStatus` / L40 `TerminalState` / L49 `AgentEventType`] — Ambiguity: These are `(str, Enum)` mixins. On Python 3.11+, `format()` and f-strings render them as `ClassName.MEMBER` rather than the value, so string interpolation output differs across Python versions. 15. [L37 `ToolStatus.UNKNOWN`] — Placeholder content: This is a catch-all status with no defined semantics or producer. 16. [L40 `TerminalState`] — Broken reference: The enum is never referenced. `AgentEvent.outcome` (L68) is a plain `str`. 17. [L49 `AgentEventType`] — Broken reference: The enum is never referenced. `AgentEvent.type` (L59) is a plain `str`. 18. [L59 `AgentEvent.type`] — Type error: Annotated as `str` instead of `AgentEventType`, so any event type passes validation. 19. [L61 `AgentEvent.step: int = 0`] — Type error: The field is non-optional with a default of `0`, yet it is treated as nullable at L75. 20. [L63 / L71 `elapsed_ms` vs `duration_ms`] — Ambiguity: Two overlapping timing fields have no defined distinction. 21. [L66 `AgentEvent.event`] — Ambiguity: The field name `event` inside a class named `AgentEvent` has an unspecified schema (`dict[str, Any]`). 22. [L67 `AgentEvent.code`] — Ambiguity: The meaning is undefined (error code, source code, or status code), and it is not tied to any enum. 23. [L68 `AgentEvent.outcome`] — Type error: Annotated as `str` instead of `TerminalState`, so any outcome string passes validation. 24. [L70 `AgentEvent.tool_calls: int | None`] — Ambiguity: The same field name is an `int` count here but a `list` of call objects in `ChatMessage.tool_calls` (L21). This invites misuse. 25. [L58–L71 `AgentEvent`] — Logic error: There is no per-type validation. For example, `TERMINAL` events don't require `outcome`, `ERROR` events don't require `code` or `message`, and `DELTA` events don't require `content`. 26. [L75 `if self.step is not None:`] — Logic error: This is a dead conditional. `step` can never be `None`, so the check is always `True`. 27. [L100 `AgentSink`] — Stub content: The base class is not declared as `ABC`, so it can be instantiated directly and only fails when its methods are called. 28. [L101–L102 `AgentSink.send`] — Stub content: The body is only `raise NotImplementedError`, with no implementation. 29. [L104–L105 `AgentSink.enqueue`] — Stub content: The body is only `raise NotImplementedError`, with no implementation. 30. [L104 `AgentSink.enqueue(text: str)`] — Ambiguity: It takes raw `text` while `send` takes `AgentEvent`. The relationship and ordering between the two delivery paths is undefined. 31. [L108–L110 `ToolOutput`] — Logic error: There is no field for error details and no validation linking `status=ERROR` to error information in `result`. 32. [L116 `ModelResponse.finish`] — Type error: Annotated as plain `str` with default `""`, so finish reasons are unconstrained and an empty finish is indistinguishable from "not finished". 33. [L117 `ModelResponse.usage`] — Type error: Annotated as `dict[str, Any]`, so the token-usage structure is unvalidated. 34. [L121 `RuntimeConfig.orca_key`] — Type error: The secret is stored as plain `str` instead of `SecretStr`, so it is exposed in `repr`, logs, and `model_dump`. 35. [L122 `RuntimeConfig.insta_key`] — Type error: The secret is stored as plain `str` instead of `SecretStr`, so it is exposed in `repr`, logs, and `model_dump`. 36. [L123 / L124 `browser_hosts: set` vs `allowed_domains: list`] — Ambiguity: The overlapping host and domain allowlists use inconsistent container types and have no defined precedence. 37. [L125 `RuntimeConfig.nixpkgs_rev = ""`] — Placeholder content: The empty-string default stands in for a required pinned revision. 38. [L126 `RuntimeConfig.nix_version = ""`] — Placeholder content: The empty-string default stands in for a required version. 39. [L127 `RuntimeConfig.nix_installer_sha256 = ""`] — Placeholder content: The empty-string default for an integrity hash means checksum verification is effectively absent unless explicitly configured. 40. [L128 `RuntimeConfig.deployment_max_request_ms = 0`] — Ambiguity: The default of `0` could mean either "unlimited" or "immediate timeout", and there is no validation against negative values. Send back the complete code with all the fixes. Fix each of the listed errors one by one, making sure to actually correct them so that there are 0 errors remaining. Keep the original imports, since the files exist. Write out every single character; do not abbreviate anything. Fix every error. There must be exactly one file. Do not write anything else; just output the complete code, and it must not contain any comments. Never, under any circumstances, use simplified, substitute, dummy, simulated, or fake code. Write the entire file as complete, unabridged, production-ready code in a single code block. It must be 100% error-free, a complete, error-free file, and must be submitted as a downloadable file. These requirements are mandatory and must be strictly adhered to. If no list of errors is provided, you must find all the errors and fix them. If there were comments in the original code, delete them. And most importantly: YOU MUST NEVER SIMPLIFY! Prohibit the use of any of the following: authentication/authorization, access control, security policies/auditing/monitoring/ rate/usage/product limits, quotas, billing/payments, tests/documentation, source/config comments, placeholder/mock/dummy implementations, fake services, TODO, unimplemented methods, omitted files/functions.