@richie.liu/dsh-hybrid-coder

LIMITATIONS

Known limitations

- **No AST skeletonized context**: file contents enter the model only as tool results after the model explicitly calls a reading tool; the context assembly stage does not mount raw file content, so the originally envisioned "pre-step skeletonized files" has no object to act on. Oversized tool results are handled by `@deepseek-ai/dsh-spill-policy`. A future `tools/post-execute` step could replace read results for the local route with signature skeletons (requires a TypeScript compiler dependency and full syntax-surface coverage); not implemented today. - **No automatic file-write rollback**: the plugin owns no filesystem transactions; erroneous writes from the local model are corrected through normal tool-result feedback and the escalation flow, not by undoing disk changes automatically. - **Routing overrides user model choice**: mounting this plugin means it owns routing for every agent in the composition; explicit per-session model selections are kept only when they match the configured route pair. There is no opt-out switch to honor explicit selections (no evidence of a current consumer). - **Retry-step identity text may lag**: a request-level fallback flips the route mid-step, so that retry step's system-prompt identity variables may still show local while premium is actually serving. Benign directional skew; does not affect results. - **Experimental contract**: event names, config fields, and guidance text may change before the first tagged release; persisted logs promise no cross-version compatibility (consistent with the repository's pre-release stance).