Update outdated architecture and phase documentation

[groupsky]

Problem

Architecture and phase documentation mark features as "(future)" or "NEXT" that are already implemented in production.

Discovered during aspected review of #347 fix.

Outdated Documentation

1. docs/ARCHITECTURE.md

Line 9: "Polling Scheduler - Coordinates polling across devices (future)"

• ❌ OUTDATED - PollingScheduler is implemented in src/polling-scheduler.ts

Line 26: "modbus/{deviceId}/data - Device data publications (future)"

• ❌ OUTDATED - Data publishing is implemented in src/index.ts lines 68-84

2. docs/PHASES.md

Lines 23-261: Shows Phase 2 as "NEXT" but many features are implemented:

• ❌ Driver loading - IMPLEMENTED
• ❌ Device connection - IMPLEMENTED
• ❌ Polling system - IMPLEMENTED
• ❌ Data publishing - IMPLEMENTED

Line 250: "Phase 1: ✅ Complete (PR #86)"

• ⚠️ Needs update - Phase 2 features are partially/fully complete

Impact

• Confusing for new contributors
• Makes it unclear what features are production-ready vs planned
• Misrepresents current project state
• Could lead to duplicate implementation efforts

Expected Updates

ARCHITECTURE.md

• Remove "(future)" markers from implemented features
• Add implementation references (file:line)
• Mark truly future features clearly

PHASES.md

• Update Phase 2 status to reflect implemented features
• Mark completed items with ✅
• Add completion dates/PR references
• Create Phase 3 if needed for remaining work

Files Affected

• docs/ARCHITECTURE.md
• docs/PHASES.md
• Possibly packages/mqtt-bridge/docs/ARCHITECTURE.md

Related

• Aspected review of loadConfig() does not load devices from configuration #347
• Multiple PRs have implemented Phase 2 features
• Documentation maintenance issue

[groupsky]

Verification Results

I've verified the current state of the documentation against the codebase implementation.

✅ Already Fixed: Root ARCHITECTURE.md

The root docs/ARCHITECTURE.md has been updated and no longer contains the outdated markers mentioned in this issue. The features are correctly documented as implemented (no "(future)" markers).

❌ Still Outdated: Package-Specific Documentation

The package-specific documentation in packages/mqtt-bridge/docs/ is still outdated:

1. packages/mqtt-bridge/docs/PHASES.md

Current state: Shows "Phase 2: Driver Integration (NEXT)" with status "📋 Ready to start"

Reality: Phase 2 was completed and merged in:

• PR feat(mqtt-bridge): Phase 2 - Driver Integration #90 (merged 2026-01-02): PollingScheduler, DriverLoader, driver integration, data publishing
• PR feat(mqtt-bridge): add device loading from config (#337) #341 (merged 2026-02-08): Device loading from config
• PR fix(mqtt-bridge): include devices field in loadConfig() and fix type safety #352 (merged 2026-02-08): Type safety fixes

Implementation evidence:

• src/polling-scheduler.ts - ✅ Implemented
• src/driver-loader.ts - ✅ Implemented
• src/index.ts lines 68-84, 87-96 - ✅ Data publishing implemented
• src/device-manager.ts - ✅ Driver lifecycle implemented

2. packages/mqtt-bridge/docs/ARCHITECTURE.md

Current state: Multiple features marked as "(future)"

Examples of outdated markers:

• Line 9: "Polling Scheduler - Coordinates polling across devices (future)" - ❌ Implemented in PR feat(mqtt-bridge): Phase 2 - Driver Integration #90
• Line 26: "modbus/{deviceId}/data - Device data publications (future)" - ❌ Implemented in PR feat(mqtt-bridge): Phase 2 - Driver Integration #90
• Lines 10-11: State Manager and Transport Manager marked as "(future)" - need verification

Recommendation

This issue remains valid. The package-specific documentation needs updating to:

1. PHASES.md:

   • Mark Phase 2 as "✅ Complete" with PR feat(mqtt-bridge): Phase 2 - Driver Integration #90 reference
   • Update status line: "Phase 2: ✅ Complete (PR feat(mqtt-bridge): Phase 2 - Driver Integration #90)"
   • Add completion date: 2026-01-02

2. packages/mqtt-bridge/docs/ARCHITECTURE.md:

   • Remove "(future)" markers from PollingScheduler
   • Remove "(future)" markers from data publishing topics
   • Add implementation references to completed features
   • Verify and update State Manager / Transport Manager status

The issue description is accurate and the work is still needed.