diff --git a/CHANGELOG.md b/CHANGELOG.md
index c773b860..41a6d9fd 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -56,7 +56,8 @@ and no final release has been published.
 - Offline map reading and search now consume the independent TMAP SDK v0.1.1, locked to commit `d8fc21550859bce1c242e6330b0e9ae2ddf9eecc`. PlatformIO and CMake share the release pin; the copied reader/search implementation is removed. Native contracts and real world/China map probes validate the integration.
 - Firmware Tracker and Geocaching reuse one browsable item card with previous/next navigation and on-demand details. Main cards show distance and an approximate administrative area through a shared map-search component instead of raw coordinates.
 - Tracker cards prefer KML route names over internal revision filenames, use readable fallbacks for unnamed shared routes, remove the redundant filename status, and place paging and localized Actions in the card footer.
-- Map controls use separate upward Menu and Team menus. Menu contains contour, layer, POI-search, navigation and track controls; Help has a fixed touch Close button for devices without keyboards.
+- Tracker, Contacts, Chat, Settings, Extensions and Network use a shared bottom bar and upward filter menu, recovering the permanent sidebar width for content. Contacts/Chat air status is available on demand under Info. Existing filter widgets and page callbacks are reused; menu layout, input dismissal and transient surfaces share one component.
+- Map controls use the same bar and popup components for separate upward Menu and Team menus. Menu contains contours, a direct OSM/Terrain/Satellite submenu, Search, navigation and track controls. Team appears only while joined to a valid team; Help has a fixed touch Close button for devices without keyboards.
 - Named POI label budgets increase by approximately 40 percent while keeping the existing placement buffers and overlap checks. Actual visible density depends on available data and screen space.
 - Supported workflows use standalone device controls, browser USB and Center; Meshtastic/MeshCore Bluetooth companion-app connections are not advertised as supported.
 - Privacy descriptions distinguish private local records from voluntarily public coordinates, routes, time and author-linked metadata. Independent services avoid requiring one central account operator, but recipients can retain and analyse public data.
@@ -70,9 +71,9 @@ and no final release has been published.
 
 ### Pending final release acceptance
 
-- Before the TMAP SDK integration, the main CI suite, 148 native tests, browser and service checks, all ten firmware targets, and Linux package checks passed. The combined TMAP firmware was subsequently built and flashed on Wio L2, with original identities and all 309 configuration fields verified. The later navigation/Map/POI candidate also built successfully but has not been flashed; the latest Tracker card revision has native LVGL and target-source syntax coverage and still requires firmware-build and physical acceptance.
+- Source `0035732e` passed the full main CI suite and all ten firmware targets. Its navigation/Map/POI/Tracker image was flashed on Wio L2, with original author/RF public identities and all 309 configuration fields verified. The user confirmed the flashed Tracker/Map controls and touch Help work. The subsequent shared bottom-menu revision has native LVGL, actual-page touch and target-source syntax coverage; current-source CI and physical acceptance remain separate gates.
 - Public global-region selection, first-level boundary verification and regional queries have passed through the real WSS/Reticulum directory.
-- Physical Geocaching v1 publication and confirmation passed using the original signed record and directory proof. Same-ID update/archive remains pending; the current device rejected the update save with a storage error after transient busy replies. Physical trail v1 signing, publication and confirmation passed; successive versions remain blocked by retained staging capacity. Navigation and the latest map/card changes also require physical acceptance. Passing software tests does not substitute for these checks.
+- Physical Geocaching v1 publication and confirmation passed using the original signed record and directory proof. Same-ID update/archive remains pending: after reboot and fresh identity/configuration verification, the latest retry still returned Busy at upload admission, before signing. Physical trail v1 signing, publication and confirmation passed; a resumed attachment upload still returned LimitExceeded. Route calculation/following and the revised shared menus also require physical acceptance. Passing software tests does not substitute for these checks.
 - README screenshots, the English Wiki and release packages have been prepared. Deployment of the new Device/Tracks website, the final release date, the stable-release announcement and publication of release assets follow successful physical acceptance.
 - Stable release status will not imply identical peripherals or completed hardware validation on every target. The device support table continues to describe those differences.
 
diff --git a/README.md b/README.md
index 3141c99c..1ad89320 100644
--- a/README.md
+++ b/README.md
@@ -132,6 +132,11 @@ Previous/next navigation reuses the widgets; the current file's start position
 feeds the shared approximate-area and distance presentation. Route geometry,
 elevation and images are opened through the existing preview when needed.
 
+The card uses the full content width. **Menu** in the bottom bar selects
+**Tracks**, **Routes** or **Nav** on supported navigation targets. Contacts,
+Chat, Settings, Extensions and Network use the same bottom-menu components;
+Contacts and Chat expose their radio status through **Menu → Info**.
+
 ![Firmware Tracker card](docs/images/release-1.0.0/firmware-tracker-card-native.png)
 
 *Actual Wio native LVGL preview from CI with sample KML and simulated GPS. The
diff --git a/docs/locales/zh-Hans/web-outdoor-management/43-裸NVS入口与存储别名清单.md b/docs/locales/zh-Hans/web-outdoor-management/43-裸NVS入口与存储别名清单.md
index 54b85b9d..f3c211cc 100644
--- a/docs/locales/zh-Hans/web-outdoor-management/43-裸NVS入口与存储别名清单.md
+++ b/docs/locales/zh-Hans/web-outdoor-management/43-裸NVS入口与存储别名清单.md
@@ -2,7 +2,7 @@
 
 由 scripts/audit_nvs_access.mjs 扫描 ESP、共享 UI 和仓库 third_party 的 C/C++ 文件。只记录 NVS 函数、namespace/key/handle 实参和位置，不读取设备、不记录值/默认值/缓冲/分区名。不把最近的 nvs_open 自动推断为后续调用的 namespace；跨作用域句柄、宏和条件编译仍需人工核对。
 
-扫描 1527 个源文件，找到 106 个候选调用，分布于 8 个文件。显式打开 15，键访问 45，其余为提交/关闭/清域。调用数不是独立配置数。
+扫描 1529 个源文件，找到 106 个候选调用，分布于 8 个文件。显式打开 15，键访问 45，其余为提交/关闭/清域。调用数不是独立配置数。
 
 这是源码入口清单，不是全部配置或硬件生效证明。系统 SDK、构建环境依赖、其他平台、函数指针/包装器实参以及复杂原始字符串不由此表自动覆盖。依赖库可单独调用 collectNvsAccesses 指定根目录审计；输出应单独记录其版本，不能写进与机器无关的仓库清单。
 
diff --git a/docs/wiki/21-Trails.md b/docs/wiki/21-Trails.md
index 5a8ee324..71c13d6a 100644
--- a/docs/wiki/21-Trails.md
+++ b/docs/wiki/21-Trails.md
@@ -99,7 +99,7 @@ images. Package installation depends on firmware capabilities, storage and the
 resources included in the package. A successful browser preview is not proof
 that every KML presentation feature can render on every embedded target.
 
-The Navigation filter adds locally calculated origin-to-destination foot routes
+**Tracker → Menu → Nav** adds locally calculated origin-to-destination foot routes
 on supported targets with routing data. It reuses the existing POI picker and
 saves KML plans separately from recordings and imported routes. See
 [[24. Offline Navigation and Map Controls]] for the complete device workflow.
diff --git a/docs/wiki/24-Offline-Navigation.md b/docs/wiki/24-Offline-Navigation.md
index e9a3ab56..21b9227d 100644
--- a/docs/wiki/24-Offline-Navigation.md
+++ b/docs/wiki/24-Offline-Navigation.md
@@ -16,7 +16,7 @@ search. The terrain and satellite layers show only the zoom levels present in
 their respective packages.
 
 The current calculation runtime is available on supported PSRAM-capable Arduino
-ESP targets, including Wio L2. The Navigation filter is hidden when the runtime
+ESP targets, including Wio L2. The Nav menu choice is hidden when the runtime
 is unavailable. This integration currently calculates foot routes within one
 installed routing package. It does not offer car/bicycle profiles, runtime
 conditional-rule evaluation, or route stitching across separate graphs. Prepare
@@ -24,7 +24,7 @@ a connected regional graph in Center when a trip needs wider coverage.
 
 ## Create an origin-to-destination plan
 
-1. Open **Tracker**, choose **Navigation**, then **New navigation**.
+1. Open **Tracker → Menu → Nav**, then **New navigation**.
 2. Keep **Current location** as the origin, or choose another origin using the
    existing POI search. A current-location origin needs a valid GNSS fix when
    calculation starts.
@@ -51,7 +51,7 @@ Loading activates the route overlay and the existing route-following displays
 for current position, route progress, remaining distance, deviation and arrival.
 Stopping navigation does not delete the saved plan.
 
-Tracker keeps **Tracks**, **Routes** and **Navigation** separate. Tracks contains
+Tracker's bottom **Menu** keeps **Tracks**, **Routes** and **Nav** separate. Tracks contains
 recordings, Routes contains ordinary route files, and Navigation contains saved
 calculated plans. Each mode reuses a single card with previous/next controls.
 Route names come from KML when available; an internal revision filename is not
@@ -62,10 +62,13 @@ use the calculated result or route preview for route length.
 ## Use the Map taskbar
 
 The bottom bar keeps the zoom controls at the left. **Pos**, **Help**, **Team**
-and **Menu** appear at the right, in that order.
+and **Menu** appear at the right, in that order. **Team** is visible only while
+the device has joined a team with a valid team ID.
 
 **Menu** opens upward and contains contour visibility, map-layer selection,
-POI search, **Load navigation** and **Load track**. **Team** opens its own upward
+**Search**, **Load navigation** and **Load track**. **Map Layer** opens a second
+level with direct **OSM**, **Terrain** and **Satellite** choices, marking the
+current source. **Team** opens its own upward
 menu for member selection and member-track actions, making team operations
 accessible without entering the general tool menu. Only one menu is open at a
 time. Tap its button again or tap the map outside it to dismiss it. Long menus