refactor: change ports from 3007/3008 to 8578/8579

Avoid port conflicts with other local services. Updated across
97 source files, docker-compose configs, docs, tests, scripts,
and agent configs.

UI:     3007 → 8578
Server: 3008 → 8579

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Claude Agent

.automaker/memory/api.md

@@ -5,9 +5,9 @@ relevantTo: [auth]
 importance: 0.7
 relatedFiles: []
 usageStats:
-  loaded: 94
-  referenced: 28
-  successfulFeatures: 28
+  loaded: 99
+  referenced: 30
+  successfulFeatures: 30
 ---
 <!-- domain: Authentication & Authorization | OAuth, token management, access control -->
 
@@ -96,4 +96,9 @@ usageStats:
 #### [Pattern] localStorage key namespacing with colon prefix (`automaker:serverUrlOverride`) isolates feature data from global scope (2026-03-11)
 - **Problem solved:** Avoid collisions with other localStorage keys in shared browser environment (esp. with iframes or multiple tabs)
 - **Why this works:** Prevents accidental overwrites from other scripts; makes feature keys searchable and auditable in DevTools
-- **Trade-offs:** Gained: namespace isolation and discoverability; lost: shorter keys
+- **Trade-offs:** Gained: namespace isolation and discoverability; lost: shorter keys
+
+#### [Pattern] Master encryption key (HOMEMAKER_VAULT_KEY) is validated at VaultService instantiation and throws immediately if missing or malformed (must be 64 hex chars). This fail-fast approach prevents silent failures. (2026-03-15)
+- **Problem solved:** Securing access to encrypted secrets storage at startup
+- **Why this works:** Configuration errors for encryption keys must surface immediately in development/testing, not revealed during first encrypt/decrypt operation on production.
+- **Trade-offs:** Startup delay/ceremony (validation overhead is negligible). Forces explicit key management in all environments.

.automaker/memory/architecture.md

@@ -5,9 +5,9 @@ relevantTo: []
 importance: 0.5
 relatedFiles: []
 usageStats:
-  loaded: 316
-  referenced: 17
-  successfulFeatures: 17
+  loaded: 318
+  referenced: 19
+  successfulFeatures: 19
 ---
 <!-- domain: Content Pipeline | Validation patterns for content processing pipelines -->
 

.automaker/memory/auth.md

@@ -5,9 +5,9 @@ relevantTo: [cost-optimization]
 importance: 0.7
 relatedFiles: []
 usageStats:
-  loaded: 41
-  referenced: 12
-  successfulFeatures: 12
+  loaded: 43
+  referenced: 14
+  successfulFeatures: 14
 ---
 <!-- domain: Cost Optimization | Token usage, API cost reduction, model selection efficiency -->
 

.automaker/memory/content-pipeline-validation.md

@@ -0,0 +1,22 @@
+---
+tags: [data]
+summary: data implementation decisions and patterns
+relevantTo: [data]
+importance: 0.7
+relatedFiles: []
+usageStats:
+  loaded: 1
+  referenced: 1
+  successfulFeatures: 1
+---
+# data
+
+#### [Gotcha] Precipitation detection requires BOTH absolute check (precipitation > 0) AND probabilistic check (precipitationProbability > 30%) to be reliable (2026-03-15)
+- **Situation:** Implementing isPrecipitationExpected() helper for maintenance scheduling; single check was unreliable with real weather API data
+- **Root cause:** OpenWeatherMap data can have precipitation=0 but high probability, or vice versa; both fields have different meanings. Using only one misses rain events.
+- **How to avoid:** Easier: explicit dual logic is clear. Harder: more complex than single threshold; different from typical rain detection patterns
+
+#### [Pattern] Forecast aggregation strategy: 3-hour intervals aggregated to daily summaries with preference for noon readings over other times (2026-03-15)
+- **Problem solved:** OpenWeatherMap free tier returns 5-day forecast in 3-hour buckets; need to expose as daily summaries to maintenance scheduler
+- **Why this works:** Noon readings most representative of day's conditions; avoids midnight/early-morning anomalies; reduces data volume while preserving accuracy
+- **Trade-offs:** Easier: daily API contracts simpler. Harder: loses intra-day variation; if weather changes dramatically mid-day, missed in daily summary

.automaker/memory/cost-optimization.md

@@ -5,9 +5,9 @@ relevantTo: [documentation]
 importance: 0.7
 relatedFiles: []
 usageStats:
-  loaded: 375
-  referenced: 92
-  successfulFeatures: 92
+  loaded: 381
+  referenced: 94
+  successfulFeatures: 94
 ---
 <!-- domain: Documentation | Docs standards, structure, maintenance patterns -->
 

.automaker/memory/data.md

@@ -0,0 +1,17 @@
+---
+tags: [gotcha]
+summary: gotcha implementation decisions and patterns
+relevantTo: [gotcha]
+importance: 0.7
+relatedFiles: []
+usageStats:
+  loaded: 2
+  referenced: 2
+  successfulFeatures: 2
+---
+# gotcha
+
+#### [Gotcha] Worktree lacks node_modules, preventing local TypeScript verification. Must use tsc from sibling worktrees to distinguish module-resolution errors (pre-existing) from logic errors (none found). (2026-03-15)
+- **Situation:** Trying to verify TypeScript build in feature-maintenance-scheduling-ui-view worktree
+- **Root cause:** Worktree isolation uses git worktree without duplicating entire node_modules; shared monorepo tooling approach
+- **How to avoid:** Lightweight worktree but requires knowledge of sibling tooling locations; type safety verified indirectly