Binance fee dataset never lands in OSS

[proerror77]

7 天 OSS 审计发现 venue=binance_usdm/dataset=fee/ 在 bucket 中不存在，但 collector 有 binance_fee_upload.rs 支持，且 lob-pit-materializer 要求 fee artifacts。确认 fee 快照/上传 timer 是否部署、上传目标前缀是否写对。

[proerror77]

Runtime preflight — 2026-08-17

Controller: Codex task /root (read-only audit only).

Target readback on monday-trade-data-26 / i-6we6afeqsvv8uo1ixmyo:

• /data is mounted and the existing USD-M reference collector/upload units are active; fresh reference triplets are being produced and OSS upload status reports success.
• binance-fee-snapshot, binance-fee-snapshot-upload, all fee units, /data/monday/spool/binance-fee, and its upload status are absent.
• /etc/monday/credentials/binance-account.json is absent or invalid. No credential contents or alternate secrets were read.
• Exact source is origin/main@3da03f455479a76e9b86377f5a03edcc5fde1601; collector release run https://github.com/proerror77/monday/actions/runs/31989922037 is publishing the existing release bundle for that source.

Terminal result: BLOCKED before Runtime. Installing timers without the atomic account credential would create a known failure, so no binary, unit, spool, OSS object, collector, order, Paper, Shadow, or Live mutation was performed.

Required human action: provision the existing credential contract at /etc/monday/credentials/binance-account.json through the authorized secret-management path. After that, deploy the exact release bundle with digest verification, enable the three existing timers, and require OSS fee.json / manifest / _SUCCESS readback before this issue can close.

[proerror77]

Exact release ready — 2026-08-17

Release run https://github.com/proerror77/monday/actions/runs/31989922037 completed successfully for exact source 3da03f455479a76e9b86377f5a03edcc5fde1601.

• Collector image: binance-lob-archiver@sha256:015dd7febc474073560ecfc283f4d8c7bbe27854563f1855140776fe1fe0448e
• Release artifact: binance-lob-archiver-linux-amd64-3da03f455479a76e9b86377f5a03edcc5fde1601, GitHub artifact digest sha256:7408e43c354f9d31ccce72dc3d06d9d90168bcfb9bb96a02dba87e90d0b92362
• Fee producer SHA-256: 01fcd9a4f5075142f53366f13bad14507df2f54c9e616782a157563a3652cc33
• Fee uploader SHA-256: ebc501a01195648df89918ac202a272a00d96da1378d34913c54a8de156be0e6
• Control archive SHA-256: c9d2bc4fc2a842efbb9f4d109a9fc137aeea79075d4d0e3c88309d5ab3badd01

Downloaded artifact checksums and the authenticated monday.binance_fee_release.v1 manifest all verify. State is now Release complete, Runtime blocked by the absent authorized account credential recorded above. No host mutation was attempted.

[proerror77]

Runtime blocker re-read — 2026-08-17T06:15Z

Read-only Cloud Assistant invocation t-jpn6u8oe7xbjvnk on monday-trade-data-26 confirms the blocking input is unchanged:

• /etc/monday/credentials/binance-account.json: missing. No credential contents or alternate secrets were inspected.
• /opt/monday/bin/binance-fee-snapshot and binance-fee-snapshot-upload: absent.
• All six existing fee service/timer units: LoadState=not-found.
• /data/monday/spool/binance-fee: absent.

The authenticated release remains ready from source 3da03f455479a76e9b86377f5a03edcc5fde1601: producer 01fcd9a4f5075142f53366f13bad14507df2f54c9e616782a157563a3652cc33, uploader ebc501a01195648df89918ac202a272a00d96da1378d34913c54a8de156be0e6, control archive c9d2bc4fc2a842efbb9f4d109a9fc137aeea79075d4d0e3c88309d5ab3badd01.

State remains Release complete / Runtime blocked. A partial install was deliberately not created before the authorized atomic secret exists; therefore no fee timer, spool, or OSS mutation occurred.

[proerror77]

Runtime blocker readback — 2026-08-17T08:32Z

Read-only Cloud Assistant invocation t-jpn6u90obcxqqkg completed Success with exit code 0 on i-6we6afeqsvv8uo1ixmyo:

• /etc/monday/credentials/binance-account.json: missing; no credential contents or alternate secret locations were inspected.
• /opt/monday/bin/binance-fee-snapshot and binance-fee-snapshot-upload: absent.
• All six fee service/timer units remain LoadState=not-found.
• /data/monday/spool/binance-fee: absent.
• The independent USD-M reference lane is healthy and uploaded successfully at 2026-08-17T08:32:26Z, so public reference acquisition is not the current blocker.

State remains Release complete / Runtime blocked by the authorized atomic account credential. No binary, unit, timer, spool, OSS fee object, collector, order, Paper, Shadow, or Live mutation was performed.

[proerror77]

Runtime blocker re-read — 2026-08-17T08:39Z

Read-only Cloud Assistant invocation t-jpn6u918g2s7d34 completed Success with exit code 0 and confirms the same atomic deployment boundary:

• /etc/monday/credentials/binance-account.json: missing.
• /opt/monday/bin/binance-fee-snapshot and binance-fee-snapshot-upload: absent.
• All six fee service/timer units: LoadState=not-found.
• /data/monday/spool/binance-fee: absent.

The authenticated fee release was downloaded again and its producer, uploader, control archive, and release-manifest checksums all passed. It was not partially installed without the authorized credential. No secret contents, alternate secret locations, timer, spool, fee object, Paper, Shadow, LiveSmall, order, or trading state were touched.