50 Commits

Author SHA1 Message Date
bench
1dcf331c90 Gates: compute must run on the BPU; board latency budget and the original model on the board CPU as speed floors
- 06-hbm records the convolutions/matmuls hb_compile left on the CPU (its node table's ON column); G1 fails on any
  when the batch's gates say require_bpu_compute (new in gates.yaml; frozen batches without it are not judged)
- batch creation freezes agent/speed_ref/<job>.json into G4: latency_budget_ms = 1.5 x board_latency_ms (median
  board latency of plain int8 builds) and cpu_fp32_latency_ms; G4 also fails when the model is not faster than
  the original FP32 model on the board CPU, and records the speedup
- scripts/board_refs.py computes both; the CPU number is onnxruntime on the board itself under the board lease
- e2e prompt states the three rules; agent/VERSION 25

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 00:41:02 +08:00
bench
e0c224f881 Pose: keypoint shift is recorded, no longer a pass/fail gate
The 2 px limit was a hand-set number from the first baseline (9-15): mean distance of all 17 joints in raw image
pixels, invisible joints included, not scale-normalized. On 10-22 SimpleBaseline r101 failed it with OKS-AP 68.34
vs FP32 68.22. OKS-AP already scores the task against ground truth with person-scale normalization, and FP32/quant
agreement is G2's job. New runs drop it from G3; the shift is still measured and recorded. Pose contracts no
longer state it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 07:55:51 +08:00
bench
8a1ee24338 Pose shift check no longer requires official_model; pose contracts state the 2 px keypoint shift limit
RTMPose evidence never carried official_model, so the top-down shift check reported every rtmpose run
UNVERIFIED (06 x2, pilot x2). run_quant already rejects a baseline of another model, so the key added nothing.
The contracts now say G3 also bounds the mean keypoint shift (2 px), which pilot agents could not know.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 01:39:15 +08:00
bench
a8fdb288ec io-contracts for every adapter family: pose (HRNet/SimCC/MSPN/RTMO), depth, flow, features, DETR/Mask2Former/SOLO, EfficientViT-seg, SSD300
139 adapter models, 16 contract files. Each output is defined as an official module's own output (verifiable
against the official source and the bench stage run export signature), plus what the platform decodes on the host.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 22:02:02 +08:00
bench
8fb9349907 Agent no longer gets the platform's model code; each task states its I/O contract
The agent could read and copy harness/adapters (model loading, preprocessing, export, decoding), and every
bench dev container carried the whole harness, registry, scripts and export trees, evaluator and gates
included. That did the model-specific half of the deployment for it.

- guard and private-home jail no longer expose harness/adapters; bench dev packs only container_site
- the evaluator still decodes outputs with the platform's own code, so agent/io-contracts states what the
  graph's inputs and outputs mean (9 families, 71 models so far); the prompt appends the task's contract
- SYSTEM.md: says where official sources, weights and environments are; the compile.yaml template is
  replaced by the facts that differ from the docs
- e2e prompt: whole-class int16/float fallback and >1.5x board latency do not pass
- agent/VERSION 24

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 21:51:17 +08:00
bench
abc351cdc5 opencode: seed the config dir with OpenCode's own package files
A hand-written package.json without its lock made OpenCode reify again over the
symlink. With its package.json + package-lock.json and node_modules linked to
the pinned copy, startup to init is 0.1 s and the home 672 KB (VM probe).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 11:08:17 +08:00
bench
d166593ec6 opencode: Pi's path guard and the pinned plugin deps instead of a per-rollout install
The bench plugin applies guard-core like Pi's private-home path-guard: file
tools against the allowlist, bash only for root scans and direct shared-
resource commands; external_directory is left to that guard (job.json was
unreadable). Each rollout's config dir now links the pinned
agent/opencode/node_modules and models.json is not fetched: startup no longer
installs ~160 MB over the network.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 10:54:18 +08:00
bench
a595d49c05 opencode: budget counts fresh input and output, not cached context, like Pi
A staging rollout (mobilenet.v2) hit 2M tokens at turn 63: 1.95M were cache reads
of the same context. Pi on the same task counted 120k for 96 turns.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 19:40:51 +08:00
bench
5fb89d66b1 opencode: terminal_exec and the quota broker, like Pi
terminal_exec's body moves to agent/extensions/terminal-core.js, shared by
Pi's terminal.ts (unchanged schema/behaviour) and OpenCode's bench.ts.
OpenCode rollouts now get a managed Execution and a broker-scoped token
(the upstream key no longer enters its environment); terminal requires both.
No checkpoint/resume for OpenCode yet: the resume scan skips it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 12:46:53 +08:00
bench
4b5b118909 terminal_exec: wait for a ticket queued behind the rollout's own worker
The stage worker runs one ticket at a time, but terminal_exec wait_handle gave up
after 1 s if the ticket had no operation yet ("Unknown protected stage handle").
10-20 staging: `bench stage run baseline` during a 40-minute bench dev compile,
and the agent followed the printed "# Pi wait" hint straight into that error.
In the last 3 days 85% of these errors (production 05/06 and staging) were real,
submitted tickets. A submitted ticket now waits under the execution's own stop
and deadline checks; a ticket the worker rejected before admission says why;
a handle that was never submitted is still unknown.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 01:55:47 +08:00
bench
ed962b11cc Agent commands: say when an earlier pipeline step failed
Pi's bash tool (shellPath), bench dev and the board terminal run commands with
pipe-note.sh: the exit code stays the last step's (no pipefail, so | head is
still 0), and a failed earlier step of the final pipeline gets one stderr line.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 16:52:42 +08:00
bench
0da66edde0 Resume rollouts after the collector dies (crash, kill, reboot, planned handover)
Processes are disposable; rollout state is resumable. When the collector dies,
the next one reconciles each running rollout from durable state instead of
quarantining or losing it:

- execution: a process of an earlier boot on this host is DEAD; a top-level
  reaper whose owner (the collector) died still proves its subtree empty
  (scopes record the owner that started them); reconcile() pauses a rollout
  with a proven-clean crash checkpoint as CONTROLLER_RESTARTED and marks its
  running tool calls INTERRUPTED; resume() across a reboot rebases monotonic
  clocks by wall time and credits the downtime as a pause
- stageworker.settle_interrupted: an admitted step whose executor is gone ends
  as STAGE_EXECUTOR_EXIT (free compile) and its handle is told directly; a
  board step without a clean board receipt still quarantines; nothing replays
- collection_runtime.crash_checkpoint: capture the real system prompt, freeze
  the session at the last saved message (mid-work phases only); configure_pi
  skips a generation ID the ledger already completed
- pi_session.js: checkpoint after every saved message (and compaction); on a
  recovered resume drop an unfinished trailing reply and answer open tool
  calls with an honest "interrupted by a platform restart" result
- scheduler: a paused rollout's local slot held by a dead holder is released
  once every process is proven gone
- pipeline: SIGUSR1 = planned handover (stop claiming, let board steps
  finish, shorten in-flight request holds, exit); SIGTERM still drains
- export: bench_recovery closes the cut segment; the dropped unfinished reply
  is excluded (UNFINISHED_BEFORE_RESTART)
- tests: test_controller_restart (real Pi on Linux: kill -9 mid-command,
  kill -9 mid-reply, SIGUSR1 handover, power loss + reboot), test_settle_
  interrupted; three tests of the old quarantine-everything rule now assert
  the new outcome while keeping their guarantees (no replay, unrelated PID
  untouched, board lease kept)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 09:29:26 +08:00
bench
18379401e4 v23: hand context compaction back to Pi, cut process rules from the prompt
- broker: a context-window 400 fails its generation (fences nothing) and goes
  back to Pi as context_length_exceeded, so Pi compacts and resends
- runner: new generation ID after compaction, wait for Pi's resumed run,
  record kept_messages; drop agent/context-mask.js and context_mask_chars
- models.json: contextWindow large so Pi compacts only on a real overflow,
  never on an estimate right before a pause (resume would not match)
- export: compactions[] gives what the model actually saw after each one
- prompt: keep facts and acceptance, drop how-to rules and coaching
  (SYSTEM.md 89->64 lines, e2e.md 27->20); stage status == stage wait

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-17 17:04:58 +08:00
bench
b248a28fd7 上下文满记为预算用完;broker 内部错误可续跑并记日志;断线只占账号 2 分钟;04 Qwen 只发出时省去最早的工具输出
- quota:400 且正文说上下文超长(vLLM maximum context length、GLM exceeds max length)记 CONTEXT_TOO_LONG,不续跑;
  rollout 结束记 CONTEXT_BUDGET_EXHAUSTED(结局 BUDGET_EXHAUSTED,rollout.json TIMEOUT),不再是 INFRA。10-16 当天 7 条 Qwen。
- quota:do_POST 吞掉的异常打出类型、消息、位置(不含请求);一次都没发出去的 generation 记 BROKER_ERROR 暂停,
  能像连不上一样续跑。10-16 05 hrnet.w32 白跑 2.9h。
- quota:连接被断(REQUEST_CONNECTION_INTERRUPTED)的请求只占账号 UNKNOWN_HOLD_S=120 秒,不再等到请求自己的期限
  (20–27 分钟、整个账号的轨迹全停)。
- agent/context-mask.js:配置 rollouts.context_mask_chars 时(只给 04 Qwen),发出的上下文超过这个字数就把最早的工具输出
  换成占位,降到 60% 以下;会话文件保留原文;切点只在再次超限时移动。Pi 自带压缩只在两次 prompt 之间触发,用不上。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 15:37:55 +08:00
bench
21fce5e2e0 v22:bench stage wait 只看一眼不轮询;板上自测先查大小、拒绝有原因、失败也删副本;速度参考编不出来写 unavailable
- bench stage wait(stageclient 与 stagerun 两个入口)不再睡,没结束就返回 2 并指向 terminal_exec wait_handle。
  10-16 efficientvit.b0 400 轮里 307 轮是轮询。
- bench dev --board:先用 salty storage ls 量开发环境里的目录(>512 MiB 或 >40 个子目录直接拒绝),
  取回后已到时限也明确拒绝;拒绝原因作为命令结果回给 agent;snapshot/dev-files/tar 在任何路径都删。
  10-16 四次自测三次从 1.2 GB 的目录提交,取回 40 分钟、超时、exit 2 无原因、VM 留下 2.5 GB。
- speed_ref:默认配置编不出来时写 latency_ms_est=null、status=unavailable,并补齐以前的 FAILED。
- SYSTEM.md 对应三处;agent/VERSION 22。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 15:24:22 +08:00
bench
e543d7bd5f bench stage wait 一次最多等 10 分钟(原 60 秒),结束就返回
10-16:轮询的 agent 每分钟烧一轮,efficientvit.b0(v18)400 轮里 302 轮是 bench stage wait,没编译就用完预算;
vkitti.base 73 轮、zoedepth.nk 55 轮。bash 一条命令上限约 14 分钟,10 分钟在内。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 06:39:50 +08:00
bench
dbb717fba8 v21:校准图片换成训练集原图(calib-raw/<set>/images,原尺寸,images.json 带顺序、来源、姿态题人框)
v18-v20 的轨迹继续用它们开始时的缩放 png/,从 v21 起 $BENCH_CALIB_IMAGES 指向 images/。原图从 36 的 JuiceFS 取
(COCO 走官网、ImageNet 从同一批 parquet 行、NYU 从官方 .mat,哈希与平台一致),ADE20K/HPatches 从 pool。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 05:29:21 +08:00
bench
22bf19d04e v20:板上自测直接在板卡容器里跑,S600 也开放;跑完删板上目录
用户定:板卡本身是测试环境、容器就是隔离,不再套命名空间(S600 的容器 seccomp 本来就禁)。命令在会话目录里跑,
$BENCH_OUT 拉回,会话目录照旧由 RemoteSession.close 删掉。S100P/S600 实测 0.75/0.97 ms,板上目录已删。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 04:52:13 +08:00
bench
16a9c50c8b v19:bench dev --board 板上自测(S100P),隔离环境在真板上验证过
- terminal_jail:系统目录改递归绑定(S100P 沙箱容器在 /usr 下有只读的主机挂载,用户命名空间里非递归绑定被拒)、
  加 /host_lib 和只读 /sys(BPU 运行库读核心类型)、透传板上 LD_LIBRARY_PATH(libdnn/libhbucp 在 /usr/hobot/lib)
- collector 的请求检查只认 development 目标且不能热换,所以 --board 在命令前加标记,由新进程里的 terminal.run 转成板上请求;
  只对 v18+、nash-m 开放;上传当前目录(本地文件 + 只在开发环境里的大文件,如 hbm),一次最多 30 分钟、4 GiB;跑完删副本
- S600 板卡容器的 seccomp 禁止所有命名空间,暂不开放
- 实测:rdk-sandbox 上隔离环境里 /etc/shadow、/userdata、/root 不可见、无网络,mobilenet.v2 0.79 ms,回执确认清理

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 01:18:03 +08:00
bench
80aa571a0c v18 开发环境给出本题校准图片目录 $BENCH_CALIB_IMAGES;speed_ref 加 --follow 滚动补算
10-15 夜:提示词只说把 /data/calib/ 换成 /data/calib-raw/,agent 去 /data/calib-raw 找,每条花 5-8 次 dev 命令。
speed_ref 按轮跑时一轮要等最慢的那道编完,新题排不上。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 00:57:42 +08:00
bench
1f8a7e20d1 v18:图和校准由 agent 自己做(平台不兜底),速度参考由平台预算
- 04 对 v18 起的轨迹(rollout.json 版本 >= 18,stagerun 放进 ctx.extra)要求 compile.yaml 写自己的
  onnx_model 和 cal_data_dir,缺了编译前拒绝、不占编译次数;更早的轨迹规则不变
- bench dev 对 v18 轨迹不挂平台 ONNX 和校准 npy,改挂 data/calib-raw(平台 128 张训练图,
  反归一化成模型输入尺寸的 8 位图,归一化由 agent 自己做)
- scripts/speed_ref.py:每题用默认配置在 dev 容器里编一次,hb_model_info 估计延迟写到
  agent/speed_ref/<job_id>.json(jail 里只读可见、实时更新),path-guard 放行这个目录
- 提示词:删掉自己编默认配置做参考、平台图和校准集位置;VERSION 18

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 20:46:51 +08:00
bench
41eb1d2193 agent v17:提示词删掉「评测数据只读可见」;判分 v0.8:板上磁盘满和板子连不上一样免罚
- dev 环境 10-14 起只挂校准集,VM 上 bench/data 为空,agent 已看不到评测数据,提示词与实际不符。
- 用户 10-15 定:板上磁盘满(disk_full)与 board_offline 同等处理,不扣 G2/G3、不扣超时分。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 13:53:34 +08:00
bench
9b7544a6bb 上线前加固 bench dev,写入速度要求
- 命令按墙钟截止(请求截止前 2 分钟),容器启动和排队不再挤掉结果回传的时间;实测超时命令在时限内返回 124。
- 状态轮询前 2 分钟 5 秒一次,之后 30 秒一次;上传上限 256 MiB,拷回单个 16 MiB、一次 64 MiB(Mac mini 链路约 1 MB/s)。
- salty_offload 的孤儿清理覆盖 bench dev:票已结束(例如轨迹被取消)还在跑的停掉,已结束的删作业和目录。
- 提示词:板上单帧延迟不超过平台默认量化配置模型的 1.5 倍,附自查办法;e2e.md 的 G4 同步。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 18:21:55 +08:00
bench
a92510dab8 智能体开发环境与自带图:bench dev 在 Salty 沙箱里跑命令,compile.yaml 可用 workspace 里自己的图和校准集
- bench dev:受管终端的 development 目标改走 Salty 容器(有完整工具链)。
  容器里用 user+mount 命名空间、uid nobody、去掉全部能力,只露工具链/缓存/数据(只读)和本轨迹 workspace;
  板卡密钥、其他轨迹、个人空间其余内容不可见(10-14 在 Salty 上实测,含 umount 逃逸被挡)。
  本地改动下次 bench dev 时上传,小文件拷回,大文件留在开发环境并列出。
- compile.yaml:model_parameters.onnx_model / calibration_parameters.cal_data_dir 可指向 workspace;
  04 在容器里核对输入输出与平台图一致(不一致直接拒、不占编译次数),记录图的 sha256 和校准来源。
- 配置白名单报错列出具体字段;SYSTEM.md 写明开发环境和自带图;agent/VERSION 15→16。
- 生效:stageworker/terminal/stageclient/SYSTEM.md 要重启;新配置要加 salty_remote.stages: terminal、
  terminal.enabled: true、pools.dev。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 17:49:14 +08:00
bench
f74fe00aaf hbm/bc 模拟器对比改为 agent 按需开启,只作诊断
阶段配置新增 verification_parameters.hbm_bc_samples(0–16,默认 0)。agent 用
bench stage run hbm --config <yaml> 指定 N 张校准样本,用 x86 模拟器对比 HBM 与 BC,
结果写在 G1.hbm_bc_cos_min,不改 verifier_ok:开了不会被扣分,真正把关的仍是 08-eval 板端实测。
编译配置只取三段,所以同一个 yaml 拿去编译也不受影响。适用任何有 .bc 的后端;跑失败记 None。
s06_hbm 随阶段打包,部署后马上生效(默认不跑);配置校验在 stageworker、说明在 SYSTEM.md,
都要下次重启时一起上线,否则按说明提交会被旧校验拒绝。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 12:48:17 +08:00
bench
f1f44c9d1e fix: 调度程序因读整个 events.jsonl 被 OOM 杀;message_update 不再逐 token 复制整条消息
Pi 每个 token 发一次 message_update,里面 message 和 assistantMessageEvent.partial
各带一份到目前为止的整条消息,events.jsonl 每条轨迹 300–800MB(99.9% 是它)。
budget_used 每次 read_text() 整个文件,调度程序峰值 5GB,10-11 07:08 在 10GB 的
Mac mini 虚拟机里被内核 OOM 杀掉。下游只读 message_update 的 type/delta,
完整文本在 message_end。budget_used 改为逐行读。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 09:47:41 +08:00
5617f57f08 fix: let a long bash command time out alone instead of ending the attempt
Bash has no default timeout, so any command running past the 900 s system
cap ended the whole trajectory (81 of 590 finished rollouts). Give bash a
native timeout one minute before the cap; only that command fails and the
agent continues. The persisted tool call keeps the model's own arguments.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 07:34:41 +08:00
106a96ae4a feat: raise the per-trajectory compile cap to five
Historical r20260929-04/05/06 data: a cap of 3 would have lost 19 of 142
PASS trajectories (13%); a cap of 5 loses 2 (1.4%). Prompt states the same
number; agent/VERSION 13 -> 14.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-04 22:45:26 +08:00
4332f43dab feat: cap each trajectory at three started compiles
Compile attempts are now the primary per-trajectory budget: they map to
the real compute cost, unlike turns or tokens, and make the stop reason
obvious. stagerun refuses a 4th 05-compile with COMPILE_BUDGET_EXHAUSTED
before inline calibration or slot acquisition.

- Counted from the stages ledger (05-compile rows that got a slot), so
  resume/recovery cannot reset it; a compile that timed out in the queue
  is free; recompiles after an accuracy miss count.
- Board/eval/review of the last artifact still run after the cap.
- Turn/token/wall budgets, per-phase deadlines, cleanup and API quota
  protection are unchanged as backstops.
- e2e prompt drops "no retry limit"; SYSTEM.md names compiles as the
  primary budget; agent/VERSION 12 -> 13.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-04 22:37:15 +08:00
13f1e99aee fix: distinguish empty documentation searches from tool failures 2026-09-29 18:29:59 +08:00
e1e73816af fix: recover stage registration and reclaim completed local leases 2026-09-29 12:55:35 +08:00
Codex
9af7952ab5 fix: consume tool boundaries under lock and diagnose transport errors 2026-09-23 22:00:17 +08:00
Codex
19e8cabef9 fix: point stage task guidance at managed waits 2026-09-23 21:58:49 +08:00
Codex
b81bc80875 fix: reuse managed waits and drain accepted stage work 2026-09-23 21:57:25 +08:00
f611ef29ab fix: keep managed API requests within the broker lifecycle
Pi requests could hit Node fetch's independent five-minute header deadline,
and queued requests could outlive their local client or terminal rollout.
Set header/body deadlines only for the loopback broker origin, cancel scopes
when clients disconnect or executions terminate, and retain uncertain upstream
reservations instead of retrying after cancellation. Resumable pauses remain open.

Validation: real Pi SDK accepted a response delayed 310 seconds (314.139 s test);
quota, Pi session, acceptance, cancellation, and lifecycle regression coverage.
2026-09-22 20:28:42 +08:00
Codex
068c56043f Merge managed natural-agent runtime into retained benchmark mainline 2026-09-22 15:35:28 +08:00
bench
d309109f2b pre-grind snapshot 2026-09-19: batches 1-7 adapters/probes/recipes + eval additive changes 2026-09-19 17:52:03 +08:00
bench
cd220cc81e fix: preserve deployment outcomes and export completed run data 2026-09-16 07:55:44 +08:00
bench
864c20a087 fix: regenerate configured repairs and use glm-5.3 for collection 2026-09-16 02:32:06 +08:00
bench
4a0e7d521f fix: run S100P board accuracy through the existing pipeline 2026-09-16 02:17:36 +08:00
bench
3dce78e49d sync 2026-09-15_12:38:10 d-robotics@d-roboticsdeMacBook-Pro 2026-09-15 12:38:10 +08:00
bench
5bafe1d7f4 sync 2026-09-15_12:26:22 d-robotics@d-roboticsdeMacBook-Pro 2026-09-15 12:26:22 +08:00
bench
50edd8c2a1 sync 2026-09-15_12:21:38 d-robotics@d-roboticsdeMacBook-Pro 2026-09-15 12:21:38 +08:00
bench
d191b68b88 sync 2026-09-15_11:26:25 d-robotics@d-roboticsdeMacBook-Pro 2026-09-15 11:26:25 +08:00
bench
6b443c5b6f sync 2026-09-15_09:49:07 d-robotics@d-roboticsdeMacBook-Pro 2026-09-15 09:49:07 +08:00
bench
9d1741b9fa sync 2026-09-15_09:42:56 d-robotics@d-roboticsdeMacBook-Pro 2026-09-15 09:42:56 +08:00
bench
469a71dfd6 sync 2026-09-15_09:35:36 d-robotics@d-roboticsdeMacBook-Pro 2026-09-15 09:35:36 +08:00
bench
7ee7ca7c8f sync 2026-09-15_09:01:15 d-robotics@d-roboticsdeMacBook-Pro 2026-09-15 09:01:15 +08:00
bench
833d65f45a sync 2026-09-15_08:21:18 d-robotics@d-roboticsdeMacBook-Pro 2026-09-15 08:21:18 +08:00
bench
29ef645b58 baseline 2026-09-15: P1-P3 landed; first PASS trajectory; collaboration rules (CONTRACT §12) 2026-09-15 08:10:26 +08:00