fix(geocaching): retain staged edits during SD contention

This commit is contained in:
liu weikai committed 2026-10-15 13:34:58 +08:00
1 parent 8dbb112f73
commit d953528584
7 files changed
+59 -13

No files matched your search

@@ -2,7 +2,7 @@
由 scripts/audit_nvs_access.mjs 扫描 ESP、共享 UI 和仓库 third_party 的 C/C++ 文件。只记录 NVS 函数、namespace/key/handle 实参和位置,不读取设备、不记录值/默认值/缓冲/分区名。不把最近的 nvs_open 自动推断为后续调用的 namespace;跨作用域句柄、宏和条件编译仍需人工核对。
扫描 1522 个源文件,找到 106 个候选调用,分布于 8 个文件。显式打开 15,键访问 45,其余为提交/关闭/清域。调用数不是独立配置数。
扫描 1527 个源文件,找到 106 个候选调用,分布于 8 个文件。显式打开 15,键访问 45,其余为提交/关闭/清域。调用数不是独立配置数。
这是源码入口清单,不是全部配置或硬件生效证明。系统 SDK、构建环境依赖、其他平台、函数指针/包装器实参以及复杂原始字符串不由此表自动覆盖。依赖库可单独调用 collectNvsAccesses 指定根目录审计;输出应单独记录其版本,不能写进与机器无关的仓库清单。
+15 -6
View File
@@ -19,10 +19,15 @@ On 2026-10-14 the user reserved the remaining Wio upload opportunity for final
release acceptance and became unavailable for manual device operations. Complete
remaining development and host-side verification before using it. Do not flash
intermediate or diagnostic candidates, or reset the device just to resume tests.
The last flashed source is `4be4f572`; retain the original identity, configuration
and pending publication fixture. An upload is permitted only when a release-ready
candidate actually needs the final physical acceptance run. Do not infer that an
available serial port is authorization to consume this reserved opportunity.
That reserved opportunity was subsequently consumed by combined TMAP firmware
`fbcdd8bb`, with application SHA-256
`6ab701588dca89739c4a796c39f366fc49f234f08b2bf449ed8d553460734ddc`.
The original author/RF identities and all 309 configuration fields were verified.
The later navigation/Map/POI candidate built successfully but remains unflashed;
Tracker title/card changes and the staged-draft SD contention fix are newer still.
Retain the original identities, configuration and publication fixtures. A further
upload requires a new device opportunity; an available application port is not
permission to reset or replace the running firmware.
The existing browser/native-directory track lifecycle has an opt-in physical
author mode. It requires an explicit application port, serial Python executable,
@@ -32,8 +37,12 @@ clients and retains the exact public confirmation checkpoint before writing.
Its default synthetic mode and synthetic API-bridge mode both pass locally with
two real native Reticulum directories, three signed versions, KML/attachment
reads and archived history after restart. The API-bridge check does not prove
physical USB signatures or device durability. The physical mode remains unused
until the reserved final acceptance run.
physical USB signatures or device durability. Physical mode has verified trail v1
signing, publication, directory proof and durable device confirmation. Subsequent
versions remain blocked by retained upload-slot capacity; the original checkpoint
must be preserved. Physical Geocaching v1 confirmation also passed. The same-record
update attempt returned a storage failure during draft save, so update/archive is
still unaccepted.
## Requested release deliverables