fix(trios-mesh): tri-net main branch does not compile inside trios workspace

[gHashTag]

Problem

The tri-net main branch (package trios-mesh) cannot compile when included as a Cargo workspace member inside gHashTag/BrowserOS trios because of several breakages:

1. build.rs has a type error in the metadata().modified().ok() chain that prevents any build.
2. src/bin/trios_meshd.rs and src/bin/smoke_m1.rs reference types/methods (Node, MeshError, Handshake, Delivery::Local, Hello::authenticated, etc.) that do not exist in the current library surface.
3. src/lib.rs includes gen/rust/*.rs modules that are generated stubs returning () instead of real values.

Proposed fix

Branch feat/trios-integration was created from main with the following minimal changes to make the crate compile and test cleanly inside trios:

• Fix build.rs metadata age calculation.
• Disable auto-discovered binaries (autobins = false) and remove the broken [[bin]] entries until their implementations are restored.
• Exclude the stub gen/rust/ modules from src/lib.rs.
• Inline the wire spec implementation in src/wire.rs until t27c emits valid Rust.

Verification

• cargo test -p trios-mesh: 101 passed.
• cargo clippy --all-targets --all-features inside trios: clean.
• ./build.sh in trios: passed.

Related

The same changes are saved as a patch in the parent repo at:
trios/.trinity/patches/trios-mesh-integration.patch.

Anchor: phi^2 + phi^-2 = 3 | TRINITY