fix(logging): initialize logger from config in the standalone bridge

[chiefmojo]

Problem

The standalone bridge (bridge.cts) calls bootstrapMemoryCoreFull without passing initLogging: true. The logger stays on its bootstrap-console default, ignoring config.logging.* entirely. In practice this means logging.timezone has no effect when running as a daemon — logs are always stamped UTC regardless of config.

Fix

Add initLogging: true to the bootstrapMemoryCoreFull call in bridge.cts. The non-daemon stdio path (bridge/stdio.ts) already passes this flag correctly; this aligns the daemon path.

const { core, config, home } = await bootstrapMemoryCoreFull({
  // ...
  home: resolvedHome,
  initLogging: true,  // initialize logger from config.logging (timezone, level, channels)
});

[Memtensor-AI]

Automated Test Results: FAILED

Cloud test-engine rerun against dev-v2.0.22 reached the PR code successfully after switching this run to the GitHub PR ref (refs/pull/1955/head), so the earlier fork-clone failure is resolved.

• Run: tr-3a63216e-cc0 on cloud test-engine 10012
• Scope: memos_local_plugin/unit
• Result: 62 passed, 2 failed
• Focused tests: bridge + pipeline logging/memory-core tests

Failure:

• tests/unit/pipeline/bootstrap-logging.test.ts: expected the memory log buffer tail entry timezone to be UTC, received undefined when initLogging is not requested.

Do not merge until the logging initialization behavior or the regression test expectation is fixed and cloud tests pass.

[syzsunshine219]

Automated Test Results: PASSED

Manual cloud test-engine rerun against the latest dev-v2.0.25 completed successfully.

• Run: tr-f6d7f8a4-39d on cloud test-engine 10012
• Ref: refs/pull/1955/head merged with latest dev-v2.0.25 before execution
• Scope: memos_local_plugin/unit
• Result: 71 passed, 0 failed, 0 skipped
• Duration: 16s

The prior failure was caused by the older base not yet enriching log records with the tz field: the no-initLogging test expected UTC but received undefined. With #1956 now present in dev-v2.0.25, the same regression path passes. Manual code review is still required before merge.