Skip to content

docs(handoff): current ai worker continuation doc (2026-08-09) - #166

Open
ncimino wants to merge 1 commit into
mainfrom
docs/nik-handoff-2026-08-09
Open

docs(handoff): current ai worker continuation doc (2026-08-09)#166
ncimino wants to merge 1 commit into
mainfrom
docs/nik-handoff-2026-08-09

Conversation

@ncimino

@ncimino ncimino commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Fleet-migration hand-off. Adds docs/handoff/HANDOFF-2026-08-09-ai-both-lanes.md as the current per-repo continuation doc and marks the 08-05 doc superseded.

Records: 0 open PRs (#162/#164/#165 merged), the intact sso tombstone landmine, the 7 untracked keycloak helper scripts, demoacme now down on BOTH its domain and own IP, Dilonne's two branches (matomo merge-ready, supabase needs-changes), and the A544 backup-first gate.

Narrative hand-off + board live in the WeOwn vault (engagement custody); this doc is the repo-local pointer version.

Copilot AI lite review requested due to automatic review settings August 9, 2026 16:42

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a repo-local “current handoff” document for the two-stream AI worker work (Keycloak/SSO+Gitea lane and ALLM/WeOwnChat lane), and marks the prior 2026-08-05 handoff as superseded to keep continuity while reducing ambiguity about current state.

Changes:

  • Added a new continuation handoff doc (HANDOFF-2026-08-09-ai-both-lanes.md) capturing current PR/branch status, known landmines, and next actions.
  • Updated the 2026-08-05 handoff doc with a prominent “superseded” notice pointing readers to the new doc.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
docs/handoff/HANDOFF-2026-08-09-ai-both-lanes.md Introduces the 2026-08-09 handoff snapshot and action queue for both work lanes.
docs/handoff/HANDOFF-2026-08-05-ai-both-lanes.md Marks the 2026-08-05 handoff as superseded and redirects readers to the new doc.
Suppressed comments (3)

docs/handoff/HANDOFF-2026-08-09-ai-both-lanes.md:62

  • This line includes a production domain name (matomo.weown.tools). If the intention is to avoid publishing real environment identifiers in a public repo, replace it with a placeholder (and keep the real value in the vault handoff).
- `feature/dilonne-matomo-dual-host` — **merge-ready.** A 27-line values override that pins the dual-host ingress so a helm upgrade cannot take `matomo.weown.tools` offline. Clean; no secrets.

docs/handoff/HANDOFF-2026-08-09-ai-both-lanes.md:67

  • This line embeds real external domain names. For a public repo, prefer placeholders (e.g., <TARGET_DEMO_DOMAIN>, <PROD_CHAT_DOMAIN>) and keep the real customer/domain details in the private vault handoff.
1. **A544 — put the demo chatbot on ocpa.group and rebrand the samples.** Plan (with the mandated pre-flight) is in the WeOwn vault at `Planning/2026W32/Plan - A544 ocpa.group Demo Chatbot - 2026-08-08.md`. **Phase 0 is a hard gate: a verified backup of chat.weown.dev — the `Remote backup verified:` marker plus an actual restore rehearsal — before any content edit.** That box is the one from the 2026-07-31 storage-mount incident and still has no backup cron, so the debt is now on this task's critical path. The target site is not ours to edit; we hand over the embed snippet.

docs/handoff/HANDOFF-2026-08-09-ai-both-lanes.md:69

  • This line references a concrete environment hostname. If this doc is meant to be safe for a public repo, consider using a placeholder like <DEV_ALM_HOST> and keeping the real hostname in the vault record.
3. **ALLM API-key ownership on dev.weown.tools** — create/confirm a support-account admin, mint a fresh Developer API key as that user, and stop pinning a personal user id. The standard: the ALLM admin is **WeOwn support, never a personal user**.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +39 to +41
1. **Deploy the `sites/sso` app layer, then select the `weown` login theme.** PR #159 merged and the theme is in the canonical render, but it is **not deployed and not selected** — it is inert until the realm points at it. Realm `weown-chat` → Realm settings → Themes → Login theme → `weown`.
2. **Gitea logout "Invalid redirect uri"** — prepared, unconfirmed: `post.logout.redirect.uris=https://git.weown.tools/*` on the `gitea` client in realm `weown`.
3. Mint the replacement `WEOWN_BOT_PAT` (contents:write + pull-requests:write) → repo Settings → Secrets → Actions.
Comment on lines +56 to +58
- **chattest** — live and verified (SSO + document library).
- **demoacme** — **down.** Both `demoacme.weown.dev` and the droplet's own IP return `000`. The earlier hand-off recorded "reserved IP dead, own IP works"; that is no longer true, so treat this as a droplet/provisioning failure to diagnose, not just a DNS re-point. The reserved IP remains dead.
- **test3** — not started.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants