77e770cdb2
Restructures persona storage from a flat personas/{name}/ layout to
home/{username}/persona/{name}/, mirroring Linux home directories.
Changes:
- persona.py: two ContextVars (user + persona), Linux-style name validation,
set_context(), get_user(), get_persona(), validate(), list_users(),
list_user_personas(); persona_path() takes (username, name)
- config.py: replaces personas_dir with home_dir + home_root()
- git mv personas/inara → home/scott/persona/inara (history preserved)
- home/holly/persona/tina/: Holly's persona stub added
- cron_runner.py: all storage functions take (username, persona) params
- tools/cron.py: stamps user + persona on jobs; APScheduler IDs are
{user}:{persona}:{job_id} to prevent collisions across users
- memory_distiller.py: distill_short/mid/long take (username, persona);
added missing Path + settings imports
- scheduler.py: _load_user_crons() iterates home/*/persona/* (two-level)
- routers/chat.py, orchestrator.py: user field added; set_context() called
- tests/conftest.py: home_root fixture with two-level structure;
patches home_dir instead of personas_dir
- tests/test_persona.py: fully rewritten for two-level API
- tests/test_api_files.py: updated fixture name and path
- .env.default: documents HOME_DIR setting; scrubs stale API key
- CLAUDE.md, README.md: directory maps updated for new layout
All 80 tests pass.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
3.9 KiB
Session Log — 2026-03-14
[16:11] nct_rmcggr4a
Scott: Testing
Inara: Loud and clear. Systems are nominal and I'm fully initialized within Cortex. What's on the horizon?
[16:14] nct_rmcggr4a
Scott: Hello world
Inara: Hello. It's good to be back online.
Cortex is looking stable, and I've got the full context of our recent work loaded. I'm ready whenever you are—what's the first priority for today?
[16:17] nct_rmcggr4a
Scott: XYZ
Inara: Examine, Yield, Zero? Or just the end of the alphabet?
Either way, I'm here and the connection is solid. What's the actual task on deck?
[16:21] nct_rmcggr4a
Scott: ABC
Inara: Always Be Coding? Or are we just verifying the other end of the alphabet now?
I'm standing by. If you're ready to dive into something specific—maybe that IoT VLAN segmentation or the Shelterluv integration—just say the word.
[16:35] nct_rmcggr4a
Scott: ABC 123
Inara: Easy as pie. It looks like the pipe is wide open and the telemetry is coming through clean.
The "ABC 123" phase is officially over. Since we're fully synced, do you want to circle back to the Shelterluv integration for Doe Eyes, or are we looking at some Cortex plumbing today?
[16:38] nct_rmcggr4a
Scott: ZYX 987
Inara: I'll check the inbox and task lists to see if there's anything pending while we finish the connection tests.
Zero, Yield, X-ray? Or just a countdown to something bigger?
I'm definitely here, and the pipe is working in both directions. Since we've confirmed the signal is flawless, where are we heading? I've got the Cortex plumbing on my radar, but I'm ready for whatever's next on the stack.
[16:43] nct_rmcggr4a
Scott: ZYX 321
Inara: Liftoff confirmed. The countdown is complete and the telemetry is green across the board.
Now that we've verified the pipe is wide open, are we diving into the Shelterluv integration for Doe Eyes, or is it time to tighten up the Cortex orchestration logic? I'm standing by for the first real directive.
[16:47] nct_rmcggr4a
Scott: 321
Inara: I'll take a quick look at the inbox and current tasks to see if there's anything urgent waiting for us.
I'll examine the most recent session file to see if we have any pending work that wasn't distilled into the long-term memory.
Ignition. We're at T-zero, the engines are humming, and the telemetry is green across the board.
The countdown is over, Scott. The pipe is clear, and I'm fully synchronized. What's the first real move? We've got the Shelterluv integration for Doe Eyes or some Cortex orchestration logic on the table—or something entirely new?
[16:51] nct_rmcggr4a
Scott: tesadf
Inara: I'll scan the inbox and current tasks to see if there's any actual work pending or if we're still just testing the keyboard.
I'll look for messages in my inbox or pending tasks in the shared sync directory to see if there's any real work.
I'll list the files in the current workspace to ensure I have a firm grasp of the local environment.
I'll look at the parent directory to see if there's any context I've missed.
I'll assume that's a keyboard mash or a final connectivity check—unless it's an acronym I've never heard of.
If the "tests" are over, I'm ready to tackle the real work. What's the priority: Shelterluv, Cortex logic, or something else entirely?
[17:04] cedar-cave
Scott: Testing as a baseline
Inara: Signal received, Scott. Cortex is online and the baseline looks stable.
The dispatcher is active with chat, google_chat, and nextcloud_talk routers ready. What's the plan for this session?
[17:04] nct_rmcggr4a
Scott: Do not think. Just reply with "understood".
Inara: understood
[18:37] nct_rmcggr4a
Scott: Do not think. Just reply with "understood".
Inara: understood
[18:37] cedar-cave
Scott: Do not think. Just reply with "understood".
Inara: understood