SIM-R3: printability 深化 + 零件库扩展 + propose + 电气深化 (ADR-019) #4
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "codex/sim-r3"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
基于 SIM-R2(!3)。独立测试 AT-042..044 全过(898/898、覆盖 96.35%;证据 docs/testing/evidence/sim-r3/)。D-SIMR3-1 已闭环。板级 L3 评估后缓议(ADR-019 §2.1 注)。建议按 !1 → !3 → 本 PR 顺序合并。
- docs/testing/evidence/S2.md + s2-health-card/{drive-result,health}.json: the full chain on the real S100P (inspect → code → plan → stage → run → artifacts → verify) with idempotent replay, plan invalidation, timeout and cancel all cleanup-confirmed; includes both real-device failure rounds (ssh user, relative runs-root) and their fixes. - scripts/drive_s2_health_card.py: default to sunrise@192.168.127.10. - scripts/install-device-helper.sh: install wipes the managed lib dir (pip --target never replaced stale code). - docs/09: current task is S2; slice 1 recorded, remaining slices listed.ADR-016 §2 mandates that a simulation/board_in_loop pass never counts as hil acceptance and that the report layer forcibly separates (报告层强制分 列). report_task now also returns environment_outcomes: verification results are aggregated per environment group, so a grasp that passed in Webots reports {"simulation": "passed"} — never a "hil" key. Runs without provenance group under "unknown" instead of defaulting to hardware. The existing aggregate outcome semantics are unchanged, and the budget-exhausted early return carries the field too. Registers AT-028 in ACCEPTANCE_TESTS.md and maps ADR-016 §2 → TestReportEnvironmentSeparation in TRACEABILITY.md. Student journey: a boardless student's passing simulation run reads as "simulation: passed", never as hardware validation (honest-result spirit of CFR-025). Gates: ruff/format clean; 574 unit tests pass (5 new); integration + acceptance 30 passed.A single 0600 file ~/.rdk/anthropic-config.json ({baseUrl,apiKey,model}) covers the custom-gateway case where all three differ from the Anthropic defaults. Env vars still override field-for-field. Keychain and the plain keyfile remain as key-only fallbacks. Tests +2 (gateway config, env override).The product agent loop now completes end-to-end with a real LLM on the real S100P, not just the scripted model. Three root causes found and fixed by driving Qwen then kimi-k3 against the board: 1. rdk-develop SKILL.md was never reaching the model (noSkills suppresses discovery; no skill-read tool is allowlisted). Inject the SKILL.md body into appendSystemPrompt alongside task-summary.md — the one channel the model always reads. Added a concrete Run manifest shape example (entrypoint/requirements/resources/artifacts/verifiers) so models stop inventing {steps,capabilities,intent,...} schemas. 2. device.inventory rejected free-text 'reason' (TS advertises Type.String, host enforced InventoryReason enum) — a contract mismatch that stalled every non-Claude model at inventory. Host now coerces unknown reason -> USER_REQUEST and drops unknown targets (DeviceInventoryParams validators). 3. task-summary.md said 'M0 only fake-001, S100P does not exist' — stale, biased models into refusing s100p-001. Updated: s100p-001 is a verified real-device target; rdk_device_list empty on a fresh state dir does not mean unavailable; inventory the user-named device directly. Real-device result (kimi-k3, ai-api.d-robotics.cc/v1, openai-responses): inventory -> write -> checkpoint -> plan (valid manifest) -> run_start -> run succeeded / outcome=passed / exit=0 / cleanup=confirmed on the S100P. Residual: the model did not task-bind the run (created the task after run_start), so task_report couldn't aggregate — workflow-ordering gap, not a run defect; the run itself passed verifiers on real hardware. Gates: pytest 664, pi 24/5skip, surface 65/0/4, ruff/mypy clean.Checkout
From your project repository, check out a new branch and test the changes.