High-performance browser automation bridge and multi-instance orchestrator with advanced stealth injection and real-time dashboard.
docs: update memory - hash-based ID system implemented (BONUS before Phase 6)
Mario4aabd6e4058c
diff --git a/memory/2026-02-28.md b/memory/2026-02-28.mdindex 5f1c5a01..ebf08777 100644--- a/memory/2026-02-28.md+++ b/memory/2026-02-28.md@@ -329,6 +329,72 @@ curl -X POST http://localhost:9867/instances/work-9868/stop- No lazy-init delays on first navigation request- Better UX: instance ready → navigate immediately+### ✅ BONUS: Hash-Based ID System (Commit fb566e7)++**Problem Solved:**+- Old design: Instance ID was name-port format ("work-9868") - leaks implementation details+- IDs were unstable if port changed+- Hard to generate UUIDs or proper IDs++**Solution Implemented:**+1. **Created IdManager** (`internal/idutil/idutil.go`):+ - `ProfileID(name)` → prof_XXXXXXXX (stable hash of profile name)+ - `InstanceID(profileID, name)` → inst_XXXXXXXX (hash of profile ID + name + timestamp)+ - `TabID(instanceID, tabIndex)` → tab_XXXXXXXX (hash of instance ID + tab index)+ - `IsValidID(id, prefix)` helper to validate ID format+ - All IDs are 8-character hex hashes (256 bits) with prefix++2. **Updated bridge.Instance structure:**+ - `ID: string` → Hash-based instance ID (inst_XXXXXXXX)+ - `ProfileID: string` → Hash-based profile ID (prof_XXXXXXXX)+ - `ProfileName: string` → Human-readable name for display (dashboard only)+ - `Port: string` → Implementation detail (kept for backward compat, optional)+ - Removed old `Name` field++3. **Updated bridge.InstanceTab structure:**+ - `ID: string` → Hash-based tab ID (tab_XXXXXXXX)+ - `InstanceID: string` → Hash-based instance ID+ - Removed old `TabID` field++4. **Integration:**+ - Orchestrator generates IDs using IdManager on instance creation+ - All handlers and dashboard updated to use new ID structure+ - ProfileManager updated to use IdManager for profile IDs+ - All tests updated and passing++**Benefits:**+- ✅ Collision-resistant: SHA256-based hashes+- ✅ Stable: ProfileID("work") always produces same hash+- ✅ Portable: IDs independent of port/location+- ✅ Centralized: All ID generation in one place (IdManager)+- ✅ Clear semantics: Names are for humans, IDs are canonical++**API Impact:**+Before:+```json+{+ "id": "work-9868",+ "name": "work",+ "port": "9868",+ "profileId": null,+ "profileName": null+}+```++After:+```json+{+ "id": "inst_a1b2c3d4",+ "profileId": "prof_x9y8z7w6",+ "profileName": "work",+ "port": "9868"+}+```++**Ready for Phase 6:** All API responses now use proper hash-based IDs!++---+### 📋 Phase 6: Comprehensive End-to-End Testing (READY FOR NEXT SESSION)**Proposed testing approach:**1. **Manual E2E workflow**@@ -394,12 +460,15 @@ curl -X POST http://localhost:9867/instances/work-9868/stop- ✅ Phase 3: Auto-port allocation in orchestrator Launch()- ✅ Phase 4: Orchestrator proxy routes to instances- ✅ Phase 5: Auto-initialize Chrome on instance startup+- ✅ **BONUS: Hash-based ID system** - Profiles, instances, tabs (BEFORE Phase 6)-**Total Commits:** 10 (from 4eee009 baseline)-**Total Lines Added:** ~550+**Total Commits:** 11 (from 4eee009 baseline)+**Total Lines Added:** ~670**Tests Passing:** 195+, 0 failures**Pre-Commit Checks:** 100% passing+**Latest Commit:** `fb566e7` - Hash-based IDs for profiles/instances/tabs+**What's Ready:**- Full multi-instance architecture (unlimited instances, configurable port ranges)- Complete instance isolation (Chrome, cookies, history, profiles)