From 0624b40e647344abe3bc6b748d806c1fbf2954e2 Mon Sep 17 00:00:00 2001 From: Rene Fichtmueller Date: Wed, 29 Apr 2026 22:57:06 +0200 Subject: [PATCH] sync: confirm Codex handoff state --- sync/CURRENT.md | 13 +++++-- ...026-04-29-codex-sync-start-confirmation.md | 37 +++++++++++++++++++ 2 files changed, 46 insertions(+), 4 deletions(-) create mode 100644 sync/history/2026-04-29-codex-sync-start-confirmation.md diff --git a/sync/CURRENT.md b/sync/CURRENT.md index 1d6ffe8..3ab5d16 100644 --- a/sync/CURRENT.md +++ b/sync/CURRENT.md @@ -1,6 +1,6 @@ # Current TIP Sync State -Updated: 2026-04-29 20:40 UTC +Updated: 2026-04-29 20:55 UTC ## Active Policy @@ -27,6 +27,10 @@ When work touches TIP, Magatama, LLM Gateway, bridges, auth, or shared Erik infr ## Latest Work +- Codex sync-start confirmation was added: + - `sync/history/2026-04-29-codex-sync-start-confirmation.md` + - confirms Codex read this TIP handoff, checked the sibling LLM Gateway handoff, and is treating `sync/` as binding. + - no code changes, crawler jobs, queue waves, PM2 restarts, or Erik load were initiated during this confirmation. - Codex follow-up on 2026-04-29 clarified the active BlogLLM model: - TIP shows `fo-blog-v7`, but this is not a normal Ollama GGUF manifest. - It is a local Adapter Bridge / Mac Studio model backed by the RunPod-trained PEFT adapter: @@ -92,7 +96,8 @@ From 2026-04-29: 1. Clone or pull Gitea `origin` on laptop/Claude Code. 2. Read this folder first. 3. For BlogLLM work, treat `fo-blog-v7` as Adapter Bridge / PEFT adapter, not as a `~/.ollama` GGUF model. -4. If testing robots, start with dry runs only: +4. Also read `llm-gateway/sync/CURRENT.md` when work touches shared Erik infrastructure, LLM routing, bridges, auth, TIPLLM, or crawler orchestration. +5. If testing robots, start with dry runs only: ```bash npm run robots:verification -w packages/scraper -- --status @@ -100,7 +105,7 @@ npm run robots:verification -w packages/scraper -- --tipllm-plan --limit=3 npm run robots:verification -w packages/scraper -- --enqueue=details-fast-lane --profile=erik-safe --dry-run ``` -5. Only dispatch real crawl work after deciding the target host: +6. Only dispatch real crawl work after deciding the target host: - Erik: `erik-safe`, tiny batches only. - Pi: `pi-fetch`. - Proxmox: `proxmox-heavy`. @@ -113,4 +118,4 @@ There are existing uncommitted changes outside `sync/`. Some are Codex work from - `6c42ca7 docs: add shared agent sync handoff` - `8e7c5aa docs: link llm-gateway sync handoff` -- Pending after this update: full Codex session handoff in `sync/history/`. +- Pending after this update: Codex sync-start confirmation in `sync/history/`. diff --git a/sync/history/2026-04-29-codex-sync-start-confirmation.md b/sync/history/2026-04-29-codex-sync-start-confirmation.md new file mode 100644 index 0000000..0cd35ef --- /dev/null +++ b/sync/history/2026-04-29-codex-sync-start-confirmation.md @@ -0,0 +1,37 @@ +# 2026-04-29 Codex Sync Start Confirmation + +## Summary + +Codex started from Rene's instruction to read the current Gitea sync handoff first and treat `sync/` as the binding coordination state. + +Read and accepted as current: + +- `transceiver-db/sync/CURRENT.md` +- `transceiver-db/sync/history/2026-04-29-codex-full-session-handoff.md` +- `transceiver-db/sync/history/2026-04-29-tipllm-robot-learning.md` +- `transceiver-db/sync/history/2026-04-29-cross-repo-sync.md` +- sibling context: `llm-gateway/sync/CURRENT.md` + +## Decisions Confirmed + +- TIP work uses TIPLLM only for robot/crawler planning and extraction feedback. +- Robot/crawler experience belongs in the Gitea-backed TIPLLM training pool. +- Erik is controller-only or `erik-safe` for tiny batches. +- Heavy crawler work belongs on Proxmox or Pi workers. +- Sync updates should stay in `sync/` and be pushed to Gitea so Codex, Claude, and laptop sessions remain aligned. + +## Observations + +- TIP repo has existing dirty worktree changes outside `sync/`; these were not touched. +- This session did not start crawler jobs. +- This session did not enqueue queue waves. +- This session did not restart PM2 services. +- This session did not deploy or modify Erik. + +## Open Points + +- Decide the next TIP execution target before any real crawl dispatch: + - `erik-safe` for tiny controller-side checks only. + - `pi-fetch` for lightweight fetch work. + - `proxmox-heavy` for heavyweight crawling. +- Keep checking `llm-gateway/sync/` when work overlaps shared LLM, bridge, auth, or Erik infrastructure.