docs(prompts): sync scheduler rosters — 2026-02-26

Executed `scheduler-update-agent`.
- Verified daily and weekly prompt directories against `roster.json`.
- Confirmed no drift in `daily-scheduler.md` and `weekly-scheduler.md`.
- Published completion log.

Co-authored-by: PR0M3TH3AN <[email protected]>
This commit is contained in:
google-labs-jules[bot]andPR0M3TH3AN committed 2026-02-26 18:23:03 +00:00
1 parent ece0dda09f
commit 2a3a960d7a
8 files changed
+136 -42

No files matched your search

+8 -8
View File
@@ -20,13 +20,9 @@ If `npx --no-install torch-lock init --help` prints initialization prompts, it m
---
### 3. [2026-02-25] (scheduler, daily, store, insight)
### 3. [2026-02-26] (scheduler, daily, retrieve)
### 1. [2026-02-25] (torch, scheduler, host-mode)
When running `npm run --prefix torch scheduler:daily`, the scheduler resolves config from `torch/torch-config.json` (cwd-scoped), not the repo-root `torch-config.json`.
### 2. [2026-02-25] (torch, scheduler, handoff)
A non-inter…
Memory retrieval seed for daily :: scheduler memory retrieval
---
@@ -40,6 +36,10 @@ A non-inter…
---
### 5. [2026-02-26] (scheduler, daily, retrieve)
### 5. [2026-02-25] (scheduler, daily, store, insight)
Memory retrieval seed for daily :: scheduler memory retrieval
### 1. [2026-02-25] (torch, scheduler, host-mode)
When running `npm run --prefix torch scheduler:daily`, the scheduler resolves config from `torch/torch-config.json` (cwd-scoped), not the repo-root `torch-config.json`.
### 2. [2026-02-25] (torch, scheduler, handoff)
A non-inter…
+55 -4
View File
@@ -68,7 +68,7 @@
"importance": 0.8,
"embedding_id": null,
"created_at": 1772047328158,
"last_seen": 1772075164390,
"last_seen": 1772129944428,
"source": "agent-output",
"ttl_days": null,
"merged_into": null,
@@ -119,7 +119,7 @@
"importance": 0.8,
"embedding_id": null,
"created_at": 1772049603683,
"last_seen": 1772075164390,
"last_seen": 1772129944428,
"source": "agent-output",
"ttl_days": null,
"merged_into": null,
@@ -170,7 +170,7 @@
"importance": 0.8,
"embedding_id": null,
"created_at": 1772050579374,
"last_seen": 1772075164390,
"last_seen": 1772129944428,
"source": "agent-output",
"ttl_days": null,
"merged_into": null,
@@ -272,7 +272,7 @@
"importance": 0.8,
"embedding_id": null,
"created_at": 1772073865813,
"last_seen": 1772075164390,
"last_seen": 1772129944428,
"source": "agent-output",
"ttl_days": null,
"merged_into": null,
@@ -380,5 +380,56 @@
"merged_into": null,
"pinned": false
}
],
[
"09910cbc-fb3e-4d44-8955-9b16f16f5f6f",
{
"schema_version": 1,
"id": "09910cbc-fb3e-4d44-8955-9b16f16f5f6f",
"agent_id": "scheduler-memory-daily",
"session_id": "session-mm3sewda",
"type": "batch_window",
"content": "Memory retrieval seed for daily :: scheduler memory retrieval",
"summary": "Memory retrieval seed for daily :: scheduler memory retrieval",
"tags": [
"scheduler",
"daily",
"retrieve"
],
"importance": 0.4,
"embedding_id": null,
"created_at": 1772129944414,
"last_seen": 1772129944428,
"source": "scheduler-retrieve",
"ttl_days": null,
"merged_into": null,
"pinned": false
}
],
[
"cfaa30c5-187b-4c36-8caa-205b6a8f1486",
{
"schema_version": 1,
"id": "cfaa30c5-187b-4c36-8caa-205b6a8f1486",
"agent_id": "scheduler-update-agent",
"session_id": "session-mm3sfj4i",
"type": "batch_window",
"content": "# Memory Update — scheduler-update-agent — 2026-02-26\n\n## Key findings\n- Roster json is perfectly synced with prompt directories.\n- No discrepancies found in daily or weekly rosters.\n\n## Patterns / reusable knowledge\n- Always verify file existence before assuming roster drift.\n\n## Warnings / gotchas\n- Ensure correct path prefix when running in host-repo mode.",
"summary": "# Memory Update — scheduler-update-agent — 2026-02-26\n\n## Key findings\n- Roster json is perfectly synced with prompt directories.\n- No discrepancies found in daily or weekly rosters.\n\n## Patterns / reusable knowledge\n- Always verify file existence before assuming roster drift.\n\n…",
"tags": [
"scheduler",
"daily",
"store",
"insight"
],
"importance": 0.8,
"embedding_id": null,
"created_at": 1772129973907,
"last_seen": 1772129973907,
"source": "agent-output",
"ttl_days": null,
"merged_into": null,
"pinned": false
}
]
]
@@ -0,0 +1,18 @@
{
"cadence": "daily",
"operation": "retrieve",
"runId": "session-mm3sewda",
"servicePath": "src/services/memory/index.js#getRelevantMemories",
"inputs": {
"agentId": "scheduler-memory-daily",
"promptPath": "",
"promptIntent": "scheduler memory retrieval",
"query": "scheduler | daily | agent | scheduler-memory-daily | intent | scheduler memory retrieval",
"events": 1
},
"outputs": {
"ingestedCount": 1,
"retrievedCount": 5
},
"status": "ok"
}
@@ -0,0 +1 @@
MEMORY_RETRIEVED
@@ -0,0 +1,20 @@
{
"cadence": "daily",
"operation": "store",
"runId": "session-mm3sfj4i",
"servicePath": "src/services/memory/index.js#ingestEvents",
"inputs": {
"agentId": "scheduler-update-agent",
"promptPath": "torch/src/prompts/daily/scheduler-update-agent.md",
"promptIntent": "Required startup + artifacts + memory + issue capture",
"events": 1,
"sourceFile": "memory-update.md"
},
"outputs": {
"storedCount": 1,
"summaries": [
"# Memory Update — scheduler-update-agent — 2026-02-26\n\n## Key findings\n- Roster json is perfectly synced with prompt directories.\n- No discrepancies found in daily or weekly rosters.\n\n## Patterns / reusable knowledge\n- Always verify file existence before assuming roster drift.\n\n…"
]
},
"status": "ok"
}
@@ -0,0 +1 @@
MEMORY_STORED
+7 -30
View File
@@ -1,34 +1,11 @@
**Protocol Research Findings**: The codebase uses `bip_utils` and `nostr_sdk` correctly. However, `BIP85` implementation uses `app_no=2` for symmetric key derivation, which is non-standard (usually `128` or `0`). A regression test `src/tests/test_bip85_compliance.py` was added to document and monitor this behavior.
# Memory Update - 2026-02-26
## What was done
- Ran TORCH update and doctor checks for this repository.
- Preferred dedicated `torch/` install path first, then fell back to repo-root updater flow.
# Memory Update — scheduler-update-agent — 2026-02-26
## Key findings
- `npx --prefix torch --no-install torch-lock update --force` failed with:
- `src and dest cannot be the same /home/user/Documents/GitHub/SeedPass/torch/src`
- Repo-root flow succeeded:
- `npx --no-install torch-lock update --force`
- `npx --no-install torch-lock doctor` reported `7 passed, 0 warned, 0 failed`.
- Roster json is perfectly synced with prompt directories.
- No discrepancies found in daily or weekly rosters.
## Operational note
- In this repo, when `torch-lock update` is run with `--prefix torch`, path resolution can collide on `torch/src`.
- If that occurs, running the updater from repo root is a reliable fallback.
## Patterns / reusable knowledge
- Always verify file existence before assuming roster drift.
## Resolution Applied - 2026-02-26
- Implemented same-path guards in `torch/src/ops.mjs`:
- `copyDir(src, dest)` now skips when `path.resolve(src) === path.resolve(dest)`.
- `copyFile(src, dest, ...)` now skips no-op self-copy operations for identical resolved paths.
- This aligns with upstream TORCH fix notes for self-hosted installs where package root equals install target.
## Validation After Fix
- `npx --prefix torch --no-install torch-lock update --force` now succeeds (no `src and dest cannot be the same` error).
- Update created backup: `torch/_backups/backup_2026-02-26T13-45-30-661Z`.
- `npx --prefix torch --no-install torch-lock doctor` reports: `7 passed, 0 warned, 0 failed`.
## Operator Context Note (Adam)
- `bitvid` is a different project Adam is working on.
- If a prompt context references `bitvid` instead of `SeedPass`, treat it as a likely working-directory mismatch.
- In that case, ask Adam to confirm whether the active directory/repo is correct before making changes.
## Warnings / gotchas
- Ensure correct path prefix when running in host-repo mode.
@@ -0,0 +1,26 @@
---
agent: scheduler-update-agent
status: completed
date: 2026-02-26
platform: ubuntu
timestamp: 2026-02-26T03-22-00Z
---
# Task Log - scheduler-update-agent
## Summary
The scheduler-update-agent successfully verified the synchronization between `roster.json` and the prompt directories (`src/prompts/daily` and `src/prompts/weekly`). No discrepancies were found. The scheduler documentation files (`daily-scheduler.md` and `weekly-scheduler.md`) were also confirmed to be in sync.
## Actions Taken
1. **Inventory**: Listed files in `src/prompts/daily` and `src/prompts/weekly`.
2. **Verification**: Compared file lists against `src/prompts/roster.json`.
3. **Result**: Perfect match found. No updates required.
4. **Memory**: Recorded confirmation of roster sync in memory update.
## Validation
- **Roster Check**: `roster.json` matches prompt files exactly.
- **Lint**: `npm run lint` passed.
## Learnings
- Roster json is perfectly synced with prompt directories.
- No discrepancies found in daily or weekly rosters.