Repository navigation
Description
Outcome
Provide two simple, supported open-source workflows: clean installation and migration of an existing controller/projects. The user explicitly requested this after the three Foundry acceptance stages. Build on PRs #62 and #63; keep existing tools and avoid a new framework.
Dated evidence — 2026-11-15
Operator reports authenticated LAN HTTPS inference from Macbox to Foundry; controller and Ollama managed by user-login launchd; Keychain-backed GitHub token works for HTTPS Git reads and project boards. Project importer reports 20 projects, 48 preserved historical checkouts, one pre-existing missing commit recovered and no unavailable metadata. Local migration tests verified source preservation, staged/unstaged/untracked work, stashes, linked-worktree conversion, hash/ref checks, recovery, resumability and refusal to overwrite conflicting destination work. Project importer remains a private, task-specific artifact, not a shipped supported Forge command.
Clean-install acceptance
- One documented entry point with an actionable preflight summary: host/architecture/disk, absent Homebrew, explicit supported interpreter (minimum vs CI vs target-validated versions), packaging tools, complete MCP/test lock, Ollama models and existing launcher ownership.
- Separate fresh identities from migrated identities; never print secrets. Explain durable GitHub credentials and token expiry/storage; document existing PAT compatibility and broader classic-token scope without silently granting worker access.
- Local default plus explicit private-network HTTPS, stable bind address, certificate trust/renewal/recovery, authentication and target-host readiness/inference checks.
- Idempotent service setup reusing or handing over an existing Ollama process; distinguish login service from pre-login availability. No hard-coded PIDs or host paths in the general workflow.
- Paste-safe commands, no interactive-zsh comment pitfalls or fragile long heredocs, no silent continuation after failures.
Migration acceptance
- Inventory/export separately from import/activate. Preserve credentials, task database and journal receipts with no implicit replay or endpoint rewriting; pause source submissions/reconcile changes and define source retirement/rollback.
- Include explicit repository mappings and restore only approved grants after path/file verification; report disk availability separately from controller access.
- Preserve all local branches, refs/reflogs, indexes/stashes, uncommitted/untracked files and linked worktrees; inspect shallow clones, missing objects and iCloud placeholders. Classify caches vs private configuration vs application runtime data. Never raw-copy an active database as a backup.
- Query the authenticated account, not only connector-visible repositories; include archived/empty repositories and preserve canonical target checkouts.
- Hash verification, full object checks, resumability, conflict refusal and concise source/target reports. No secret archives or raw project contents in public engineering records.
- Test on a genuinely clean target and a migration target with existing/conflicting state; document supported boundaries and recovery after interruption.
Remaining operational acceptance
Completed 2026-11-15: all three original source grants restored and audited reads verified over Foundry HTTPS. Actual-chat MCP routing moved to Foundry after full app reconnection; a 30B coding task and senior-reviewed revision ran through the native MCP tools with Macbox services off. Both old Macbox controller/Ollama LaunchAgents were saved privately, stopped and removed; their data and thin-client dependencies remain intact. See #65–#67 for evidence.
Remaining: actual login/reboot validation, explicit historical endpoint/journal reconciliation before moving any additional handoff clients, and a deliberate GitHub write test if needed. Do not start deferred off-host backup work under issue #7.
Next action
Resume clean installer/preflight and supported migration interfaces now that the MCP handover gate is accepted. Use Foundry's bounded workers for implementation proposals, with senior review and independent tests. Give the thin desktop MCP client a supported dependency/setup path rather than assuming the old host runtime directory can be deleted. Consolidate the guides and address the observed immediate stop/start bootstrap failure without assuming its cause. Runtime reports above are operator-provided unless explicitly identified as independently exercised; local/CI checks and target-host acceptance remain distinct.
Activity
kudama commentedon Nov 15, 2026
Grant reconciliation implementation — 2026-11-15: found and independently validated the existing Lua prerequisite, PR #61; 390 tests passed with current main and refreshed CI passed before merge as 2b7dc9c. Prepared PR #65 for dry-run/apply reconciliation preserving existing tokens/roles and selected-file manifests, plus audited live source checks. Local suite: 399 passed; final focused tests: 9 passed. Trial using the actual migration snapshot checked all 17 originally selected files and restored only the three omitted repository IDs, with credentials unchanged. Canonical Thoth currently lacks the approved Curator implementation files; use the preserved 31-thoth checkout for that mapping. No Foundry grant mutation or restart has been performed yet. Next action: after #65 required checks pass, apply on Foundry, restart only the controller and require allowed-read audits for all three repositories. General clean-install/migration acceptance remains open.
kudama commentedon Nov 15, 2026
Live grant acceptance — 2026-11-15: independently used Macbox’s existing scoped credential and trusted certificate to query Foundry over HTTPS. The corrected source checker passed for all three restored repository IDs with matching allowed read_repository_file audit records: training-atlas (d45ae68ab68f4c2a80b321a214c37d26), app-lightroom-synology-photos (9fe61db8ba2f44ebb963e10ac57b9ba6), thoth-curator (dba0c42e3cd04310a1199875ad51180d). No additional grants or credential changes were needed.
The initial checker failed Lightroom task 6d3e5badbd57496d93ecb1a3275c0060 with tool_denied. Found a request/instruction conflict: checker exposed only read_repository_file, controller says list first. PR #66 aligns its prompt and tool declaration with the already permitted list/read workflow; exact original denied arguments were not retained. 399 local tests passed, including regression assertions.
Operational learning still open: an immediate controller stop/start returned launchctl bootstrap error 5; subsequent diagnostics showed a valid plist, unloaded service and free port, and a later start succeeded. Asynchronous removal is a hypothesis, not confirmed root cause. Add bounded stop/restart lifecycle validation to repeatability work; do not instruct root bootstrap as a generic fix. Reboot/login acceptance and source-client retirement remain separate checks.
kudama commentedon Nov 15, 2026
Priority update — 2026-11-15: user requested actual-chat MCP handover and local development-task acceptance before returning to installer/migration work. PR #67 merged as 4672319 after 401 local tests and both GitHub checks passed. A real SDK stdio bridge authenticated over explicitly trusted HTTPS to Foundry and retrieved destination-only task d45ae68ab68f4c2a80b321a214c37d26. Existing forge_local registration was saved privately and updated to Foundry; CLI readback confirms the HTTPS URL and certificate path, with the original scoped token file retained.
The active chat still returns task_not_found for the destination-only ID, proving its old MCP process remains cached. Desktop self-UI automation is blocked, so operator restart of the MCP connection/app is required. Do not stop Macbox controller/Ollama yet. Next: after reconnect, prove this chat retrieves the Foundry-only task, execute/review a small bounded implementer task on Foundry, verify old-host task state is settled, then stop the old model/controller services and recheck MCP without fallback. Resume installer/migration improvements after this gate. No source services have been stopped.
kudama commentedon Nov 15, 2026
2026-11-15 — First repeatable-install increment merged in #68. New scripts/setup.py check runs read-only on stock Python 3.9 and reports interpreter/pip, Homebrew, existing private state/environment, default Ollama models, launchd definitions and listeners. Explicit-interpreter install upgrades packaging tools, installs full MCP/test lock and editable package, checks dependencies and runs tests. Tool-owned interrupted installs resume; matching complete installs return unchanged. Foreign/symlinked environments, malformed markers, changed inputs and existing private state are preserved rather than replaced. README now routes to docs/installation.md, separating controller, migration and remote-client paths.
Confirmed: actual Mac stock Python 3.9.6/pip 21.2.4 diagnosed and rejected; fresh local Homebrew Python 3.14.8 environment installed; 417-test full rerun passed before the additional malformed-marker test (17 installer cases now). GitHub CI passed all 418 regression tests plus fresh bootstrap/repeat on Linux and macOS Python 3.12; Checkmk job also passed. Foundry worker task 67e05e1c35934a9089fd9e1137d93809 supplied a bounded probe proposal; senior review corrected validation and verified behavior.
Not deployed to Foundry; no runtime services, identities, credentials or model state changed. This does not establish fresh physical-Mac provisioning or reboot/login acceptance. Remaining: consolidate safe identity/service setup, generalize project-history export/import and add migration failure/retry acceptance. Next: define and implement the reusable migration command around verified controller snapshots and separate project/history manifests. Keep #64 open.
kudama commentedon Nov 15, 2026
2026-11-15 — Continuing with a bounded restore-preview increment at main 055aa0a. Foundry implementer will propose a --plan path reusing existing restore staging/validation and returning before publication; Forge will review and independently test before publishing. Default restore compatibility and conflict refusal remain required. Full project-history tooling remains separate; no live Foundry changes are authorized by this code task.
kudama commentedon Nov 15, 2026
2026-11-15 — #69 merged after all four checks passed (432 regression tests; fresh environment bootstrap/repeat on Linux and macOS Python 3.12; Checkmk compatibility). Controller restore now supports --plan: identical staged validation, redacted report, cleanup before returning without publishing private state. Default restore is compatible and always revalidates after a preview. Synthetic tests cover late source-check failure and destination conflicts introduced after preview. No live Foundry preview/restore or service changes were performed.
Agent-review evidence: 7a3d07f5cbaf4d229adff1f65a0cb887 was rejected for unrelated dependency/version changes; c67edcdbe8b847ca82bc75366c5833fb failed tool_denied; cef1a2fbb99e45d6bbc6c11658c5c65b was rejected for incorrect control flow (preview placed after restore). Forge supplied the corrected minimal patch and independent tests. These are failed proposals, not successful agent implementations. The current worker grant excludes restore.py/tests; no grant expansion was made. Avoid supplying whole files plus broad tool discovery to small-context workers; context-loss is a hypothesis here, not a confirmed diagnosis.
Next: generalize private project/history artifacts with explicit source/target inputs and strict transport verification before import. Full project transfer, consolidated identities/services, and actual login/reboot acceptance remain open.
kudama commentedon Nov 15, 2026
2026-11-15 — Project transport verification increment #70 merged after all checks passed: 467 regression tests, fresh bootstrap/repeat on Linux and macOS Python 3.12, and Checkmk compatibility. New project_package.py requires a source-trusted checksums.json SHA-256 and verifies exact file/link inventory, bytes/sizes/executable flags and working-file record consistency. It rejects ambiguous paths, extra/missing files, hard-linked/special files and duplicate JSON/checkout IDs, and does not traverse directory links. It never extracts, invokes Git, imports or changes runtime grants. Documentation explicitly preserves the boundary: Git history and importer acceptance are NOT established.
Agent review: task 3cffe669a5104ef49015cac85b6c8ac6 supplied a pure path validator. Forge removed an unused import and an incorrect ban on legitimate trailing-dot filenames, then tested the corrected implementation. The verifier surrounding it and tests are Forge-written. Prior migration proposals rejected in #69 remain rejected. No claim that the agents implemented the full workflows.
This completes reviewed preview/transport-verification increments, not #64. Next implementation: explicit project inventory/export/import with independent Git object/ref/reflog/index/stash checks, conflict-safe resumability, canonical GitHub account inventory and documented handling of missing/cloud objects. Identity/service consolidation and target login/reboot checks remain open. No live Foundry state or original private artifacts changed.