6 Commits

Include renames

Author	SHA1	Message	Date
Jesse_ChenandCursor	7d667fecbf	fix(consult): treat pinched answers as failed and restore reply actions ... Incomplete Flash generations were billed as completed consultations. Fail those runs, keep the partial text, and reuse the rectification like/copy/rerun bar on ordinary chat replies. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-19 19:40:50 +08:00
Jesse_ChenandCursor	ff70ba87b0	feat(consult): deliver the route's strict method with the evidence instead of listing 1592 filenames ... Activating the skill returned 129,651 bytes, of which 99KB was a flat list of 1,592 undifferentiated file paths against 30KB of actual method. The one line telling the model to open the strict-workflow router sat inside that method, so no reference was ever opened and every answer was composed from the model's own background knowledge over server evidence. The route is already decided server-side and the skill already states which checklist each route requires, so the selection needs no model turn: read the mandated sections from the hash-pinned package and hand them to the model with the evidence they apply to. A route the router declares no checklist for is reported as such rather than filled in with another route's. The receipt now reports delivered sections separately from model-initiated reads, because only one of those is under the model's control. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-18 20:53:07 +08:00
Jesse_ChenandCursor	10ae149c58	fix(consult): check the evidence gate against the route the answer is on ... 七条路由的证据门都不是自己的：route_requirements 的键写成 relationship/finance，而 路由名是 marriage/wealth，另有 5 条路由压根没有条目，全部静默落到 general 的门。 missingLayers: [] 因此不表示证据齐备，只表示没检查过——婚姻的 UL 与财富的 D2 从未 进入检查。 同一函数另有两处判据也没接到权威来源。7 块正则用问题文本重猜领域，而领域早已由模型 声明并写进 route_packet，一句写作「情感」而非表里「感情」的提问在 marriage 路由上完全 拿不到性别解读边界。timing_layers_ready 读的是 missing_route_layers，该列表只装本路由 要求的层，于是对任何不要求 narayana_dasha 的路由恒为真，精确应期在该层根本没算出来时 也照样放行。三处的失败方向都是静默放宽，因此没有任何人报错。 三处都接回权威来源：10 条路由逐条显式列出必需层（层名限定为证据包真实构建的 section， 所以 wealth 不要求引擎不产出的 D11）、领域边界按 route 查表、出生时间边界从矫正闸门的 effective_accuracy 与 Lagna 敏感度派生、就绪判断直接读 section 状态。唯一保留文本探测 的是「用户有没有要一个具体日期」——服务端对此没有权威来源，改为 timing/annual 路由结构 性携带、文本仅作叠加，一次措辞漏判不再能把信号清零。 另外把 skillReferenceReadCount 暴露为回执的 skill.referenceReads（必填）与可观测日志的 skillReferenceReads。它此前数完即丢，而 skill_read 按设计不记成 runtime step，因此「模型 有没有真的翻开方法文档」在运行结束后无处可查。 Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-18 11:50:28 +08:00
Jesse_ChenandCursor	c8d9ec64c3	fix(consult): stop the model spending its step budget on invalid tool params ... A staging consultation calculated the chart and then returned nothing but the ensureFinalResponseText fallback. The model had made four calls to run-jyotish-consultation, and two of them never reached a calculation: they set both domains and theme, which canonicalDomainPlan rejects at execution. The schema declared those two fields as independent optionals, the description never mentioned the constraint, and the instructions actively told the model to use theme for a single-domain retry. Each attempt therefore bought a rule the contract never stated, and because the throw happens before the step-recording try/catch, it left no trace in the receipt either. Make the constraint unrepresentable instead of enforced. The model-facing schema keeps only question and domains, so Mastra refuses the pair before the tool body runs; the description states the single-array contract, and the instruction that advertised theme is gone. canonicalDomainPlan still resolves the single-value form for callers that build a plan without that schema, and is now exported so that path has its own tests. maxSteps and the abort timeout bound the same run but were hard-coded apart. One calculation takes about 20s against a 110s budget, so time is the binding constraint and three failed calculations exhaust it whatever the step count. The budget only has to cover the longest useful shape, so it moves to 8 beside the timeout with that reasoning recorded, and the recorded step list is sized to match so an exhausted run cannot truncate its own evidence. Step exhaustion was only ever inferable by counting events, since finishReason was recorded nowhere and progressive-disclosure reads never reach the public stream. Capture it as a closed enum plus a step count, normalizing anything unrecognized, and log both as controlled fields. Neither may enter the client receipt, whose step schema is strict and would fail a successful run. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-17 15:21:11 +08:00
Jesse_ChenandCursor	8169bd85f7	feat(consult): classify consultation workflow failures for diagnosis ... Every workflow fault except abort and timeout collapsed into the single calculation_failed code, and the upstream message was discarded, so a failing run left no evidence of whether the API rejected the call or returned a payload that missed the response contract. Classify failures into a closed vocabulary carried on ConsultationWorkflowError and record it as the failureCode of the runtime step. The observability tool call schema gains one controlled optional field; upstream error text stays out of logs, as that contract requires. Forward request_id to the API so a run can be aligned with its access log. Build public receipts from an explicit allowlist. The internal failure code must not reach the client contract, whose step schema is strict and would otherwise reject a successful run. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-08-17 12:44:19 +08:00
Jesse_Chen	e58bc36909	test: add agent evals and safe observability	2026-08-15 07:06:19 +08:00