Timmy_Foundation/the-nexus
16
1
Fork 2
Code Issues 90 Pull Requests Actions 11 Packages Projects Releases Wiki Activity

[modularization] Phase 2: Extract data layer — gitea, weather, bitcoin, loaders #460

Merged
Timmy merged 1 commits from claude/issue-421 into main 2026-03-24 21:28:05 +00:00
Conversation 0 Commits 1 Files Changed 11 +280 -163
Timmy commented 2026-03-24 21:26:10 +00:00
Owner
Copy Link

Phase 2 Data Layer Extraction (Refs #421)

Created 4 data modules under modules/data/:

  • gitea.js — Centralized Gitea API (commits, PRs, agent status) with shared caches
  • weather.js — Open-Meteo weather data fetch (pure data, no scene effects)
  • bitcoin.js — Blockstream block height polling, writes to S
  • loaders.js — Static file loaders (portals.json, sovereignty-status.json, SOUL.md) with caching

Updated 7 consumer modules:

  • panels.js, heatmap.js, extras.js, portals.js, effects.js, oath.js, audio.js

Deduplication wins:

  • Gitea token centralized (was hardcoded in 3 files)
  • SOUL.md cached (was fetched 3x independently)
  • Nexus commits shared cache (was fetched 2x independently)

Remaining fetch() calls (out of scope, future phases):

  • bookshelves.js (2 calls — Gitea-related, could move to data/gitea.js)
  • weather.js (2 calls — portal health check + weather API, weather fetch already extracted to data/weather.js but visual consumer still calls its own fetchWeather)

All 11 modified files pass node --check. No visual regressions expected — same data, same state writes, just centralized.

Refs #421

## Phase 2 Data Layer Extraction (Refs #421) ### Created 4 data modules under `modules/data/`: - **gitea.js** — Centralized Gitea API (commits, PRs, agent status) with shared caches - **weather.js** — Open-Meteo weather data fetch (pure data, no scene effects) - **bitcoin.js** — Blockstream block height polling, writes to S - **loaders.js** — Static file loaders (portals.json, sovereignty-status.json, SOUL.md) with caching ### Updated 7 consumer modules: - panels.js, heatmap.js, extras.js, portals.js, effects.js, oath.js, audio.js ### Deduplication wins: - Gitea token centralized (was hardcoded in 3 files) - SOUL.md cached (was fetched 3x independently) - Nexus commits shared cache (was fetched 2x independently) ### Remaining fetch() calls (out of scope, future phases): - bookshelves.js (2 calls — Gitea-related, could move to data/gitea.js) - weather.js (2 calls — portal health check + weather API, weather fetch already extracted to data/weather.js but visual consumer still calls its own fetchWeather) All 11 modified files pass `node --check`. No visual regressions expected — same data, same state writes, just centralized. Refs #421
Timmy added 1 commit 2026-03-24 21:26:11 +00:00
[modularization] Phase 2: Extract data layer — gitea, weather, bitcoin, loaders
Some checks failed
CI / validate (pull_request) Failing after 14s
Details
CI / auto-merge (pull_request) Has been skipped
Details
a1eb0ebb90 
Created modules/data/ with 4 data modules:
- data/gitea.js: Centralized Gitea API (commits, PRs, agent status)
- data/weather.js: Open-Meteo weather data fetch
- data/bitcoin.js: Blockstream block height polling
- data/loaders.js: Static file loaders (portals.json, sovereignty-status.json, SOUL.md)

Updated consumers to use data modules instead of direct fetch():
- panels.js: Uses data/gitea.js for agent status
- heatmap.js: Uses data/gitea.js for commit data
- extras.js: Uses data/gitea.js for timelapse, data/bitcoin.js for block height
- portals.js: Uses data/loaders.js for portals.json
- effects.js: Uses data/loaders.js for sovereignty-status.json
- oath.js: Uses data/loaders.js for SOUL.md
- audio.js: Uses data/loaders.js for SOUL.md

Deduplication wins:
- Gitea token centralized (was hardcoded in 3 files)
- SOUL.md now cached (was fetched 3x independently)
- Nexus commits shared cache (was fetched 2x independently)

Refs #421
Timmy merged commit 764b617a2a into main 2026-03-24 21:28:05 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
222-epic
3d-world
actionable
agent-presence
aistudio-ready
assigned-aistudio
assigned-claude
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-gemini
assigned-groq
assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-kimi
assigned-perplexity
claude-ready
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 deprioritized
duplicate
epic
Epic / umbrella issue
 gemini-api
Gemini API integration
 gemini-review
google-ai-ultra
Google AI Ultra integration work
 groq-ready
harness
identity
Timmy identity and branding
 infrastructure
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 kimi-ready
media-gen
AI media generation (image/video/audio)
 modularization
needs-design
nostr
p0-critical
p1-important
p2-backlog
performance
perplexity-ready
portal
research
Deep research and planning tasks
 sovereignty
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#460
Delete Branch "claude/issue-421"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?