Files
knowledge-wiki/channels/1562800574892744835.md
T

10 KiB

Channel Wiki: #cuga-delivery

Identity and purpose

  • Guild: home-v1 (1518726359512387766).
  • Category: skic-cuga (1562373126288048188).
  • Channel: cuga-delivery (1562800574892744835).
  • Approved implementation, tests, reviews, delivery evidence, status and blockers.
  • General coordination and comparison: cuga-general (1562373274032414780).

Authorization

RootAtSkic requested channel setup: https://discord.com/channels/1518726359512387766/1562800574892744835/1562800614461677641 Setup is not approval for autonomous delivery, deployments, recurring jobs or repository creation.

Workspace and continuity

  • Workspace: /opt/data/channels/cuga-delivery/ (artifacts, research, repositories).
  • Local runtime skill: channel-delivery-skic-cuga.
  • Route source: /opt/data/scripts/channel-wiki-sync.py, CHANNEL_SKILLS.
  • Private remote: https://gitea.lego-cloud.eu/skic-cuga-skills/channel-delivery-skic-cuga.
  • Checkout: /opt/data/channels/cuga-delivery/repositories/channel-delivery-skic-cuga.
  • Remote publication corrected after user feedback; main commit b9b30d45772127a47fb95d7d978d8a0d0b98505e verified against the remote ref. Authenticated exact-commit SKILL.md readback equals checkout and runtime bytes. Channel skills are remote-backed by default.
  • Preserve existing privacy and mention/reply behavior.

Project resources

Recorded by the general-channel ledger; reverify current state before implementation:

Verified setup

Approved CUGA development delivery

RootAtSkic authorized execution in message 1562875408842752062 after confirming CI/artifact publishing → GitOps template → generated DEV GitOps → Gondor Argo CD deployment. Ask genuine blocking questions in this channel; make routine decisions independently from actual source/platform evidence. No production scope.

  • Application: skic-cuga/cuga-agent.
  • Planned private template: skic-cuga/cuga-gitops-template; rendered dev: skic-cuga/cuga-gitops-dev. Verify collisions before creation.
  • Template and versioned nonsecret inputs own generated deployment content; regeneration must be reproducible and drift-checked.
  • Existing Bitwarden ESO and shared Gondor services; protected dev exposure, no credentials committed.
  • Completion requires real exact-head CI, immutable published artifacts, generated GitOps verification, expected Argo revision Synced/Healthy, ready workloads and application readback.
  • Durable task chain (default is the only verified installed profile): t_237a2476 discovery/contract → t_aec4d4dd CI/artifacts → t_0f3787d3 template/dev generation → t_3e1d0fdf deployment/independent acceptance.
  • Evidence resides under this channel's artifacts directory. Task creation does not mean deployed or running.

Current deployment checkpoint (2026-11-01)

  • New explicit authentication requirement: existing Erebor Keycloak is mandatory; SSH/operator isolation is not equivalent. Require server-side UI/API/tool protection, correct login/callback/logout/session behavior and no backend bypass before exposure. Existing master-realm discovery at keycloak.lego-cloud.eu verified; no CUGA client or real SSO journey verified. PR6 alone is NOT authentication implementation.
  • Task t_3e1d0fdf resumed. All three nonempty CUGA LLM Bitwarden entries verified in the existing ESO project; no model details/UUID needed from user. ALL THREE must be supplied via ESO, not plaintext GitOps.
  • Chart adaptation PR6: skic-cuga/cuga-agent#6, head3682739abce2b5bfff43113d3c20a596f8f6a9bd. Independent review PASS,176 local tests and render parity passed. Pushed/ref/raw-byte verified. CI7380 attempt1 last observed IN_PROGRESS, not merged/published.
  • Actual remaining access decision: existing robot$gondor-v1+gondor-v1 has pull ONLY in gondor-v1; fresh Harbor tokens grant EMPTY actions for both skic-cuga image/chart. Publisher identity is prohibited for runtime. No shared permissions expanded or new robot created. CUGA-only pull provisioning requires authorization within task's no-new-account/permission boundary; existing Bitwarden location is already known.
  • Source/template/DEV main pins below remain unchanged. No namespace/Applications/workload deployed, no provider call, no running URL or persistence/rollback acceptance. Template regeneration awaits new compatible chart and scoped access. Report artifacts/cuga-dev-delivery-report.md; receipts artifacts/cuga-chart-eso/. Resume same task, no duplicates.

Historical deployment checkpoint (2026-10-29; provider blocker superseded above)

  • Discord CUGA channels are frozen/read-only. Continue in Mattermost channel np8g1qwj8jf3zkraz1wuwb88nw; no new Discord posts.
  • Application main 0c39d31ccab97c7558ce0649443bd87ee3574bbf: required artifact CI7353 jobs passed; overall native suite failure retained under experimental DEV exception. Image/chart published in private Harbor.
  • Template main e635339285e4630cdd49f761b925a4e94efe5a57 and generated DEV main 58026cb74a8537c4c9b6b5599ea7dd9bbb688234 merged with green integrated CI. Fresh deployment preflight verified refs/manifests/chart and 16 tests plus exact regeneration.
  • Deployment task t_3e1d0fdf cannot activate: approved provider URL/model/dedicated Bitwarden key not supplied; no visible CUGA secret keys or CUGA Argo bindings. Existing publishing credentials work and are not runtime credentials. Separate approved pull-only ESO/Argo provisioning is required; earlier Bitwarden creation HTTP404 remains unresolved.
  • Live cluster has no CUGA namespace/Application/workload; DEV answers remain deliberately disabled. No running URL, provider call, persistence/rollback exercise or runtime acceptance claimed. Security findings remain deferred, not fixed.
  • Current report: /opt/data/channels/cuga-delivery/artifacts/cuga-dev-delivery-report.md; fresh machine receipt: artifacts/cuga-dev-preflight.json. Resume the existing task after inputs, without duplicate cards.

Current DEV checkpoint (2026-11-05; supersedes historical blockers above)

  • Session/chat acceptance t_6bebb285 rerun PASS after bounded memory repair: real browser same-thread replies at4/130/220s after login retained Copper Finch/Tuesday with no login interruption; three explicit sends/three200 replies, zero app restarts/OOM. Visible logout reached signed-out; prior cookie rejected immediately/+65s. Two independent HTTP sessions/12 concurrent reads at130s passed;100 backend and12 mocked Chromium failure/no-replay tests plus frontend build passed. Exact source6467d0f/imagef7849dc5, templatee9f84a3, DEV79f58f4 verified live. Full-hour/provider failure and approval replay are automated fixtures, not live certification. Initial knowledge-documents503 remains a nonblocking residual; Agent Config/history/security residuals remain unresolved. Evidence: /opt/data/channels/cuga-delivery/artifacts/t-6bebb285/attempt2/report.md. No attachments; no human acceptance or production/security clearance implied.
  • Dedicated board cuga-delivery. Task t_0ab4d250 deployed independently reviewed session renewal/recovery through CI, template and generated GitOps. Source6467d0f214684f010a55a38f1583e0f2cdfb835b; template40b98128b2800d83b48f8039157f017b238ace07; DEV2c2bcc074c2260b3457bb67daee7a6db8e9ca763. All five Argo apps Synced/Healthy, four ESO Ready, exact published app image ready with zero restarts; health/readiness and anonymous protection pass.
  • Authorized existing PostgreSQL/NFS storage supersedes historical SQLite assumptions. All four claim identities preserved; two active NFS claims Bound and two unused legacy CSI claims remain Pending. No storage, realm, shared edge/network or production changes in this release.
  • Required source artifact checks/publication CI passed; native lint/pgvector and informational aggregate failed. Vulnerabilities remain, not security-cleared. Existing Agent Config/history defects remain outside this task.
  • Independent acceptance t_6bebb285 on 2026-11-05 FAILED sustained chat: first real browser reply succeeded, then app OOMKilled21:03:03Z (exit137,4Gi limit,restart0→1); same-thread follow-up130s after login401. Explicit sign-in recovery worked. Two separate post-restart API sessions survived130s/12 concurrent reads; valid-browser logout and old-cookie rejection immediate/+65s passed;100 backend and12 focused mocked Chromium tests passed. Memory/process-lifecycle remediation required before resuming same acceptance task; token renewal failure itself is not established. Evidence: /opt/data/channels/cuga-delivery/artifacts/t-6bebb285/report.md, no attachments. Agent Config/history remain out of scope.
  • Exact digests, review/test/CI receipts and rollback tuple: /opt/data/channels/cuga-delivery/artifacts/t-0ab4d250/handoff.md. No unsolicited files to Mattermost; concise outcomes only. Discord remains read-only.
  • Bounded OOM repair independently reviewed and deployed by t_cdf95beb (2026-11-05): templatee9f84a30819db0ead55dc5afcde386dec71a343d, DEV79f58f48093c6f4270c6a21fbdef02f1e44ecfe8, unchanged source/image above. Only memory request4Gi/cap6Gi changed; one replica/Recreate, auth/PII/storage unchanged.105 template +100 session tests PASS; exact candidate/integrated CI7534/7537/7539/7540 PASS.5 Argo Synced/Healthy,4 ESO Ready,0 app restarts.181 cgroup samples/903s: cold peak4.895GiB, final stable3.588GiB, no max/OOM events.16 authenticated direct-HTTP same-thread replies and16 background saves passed, including135s follow-up. Not browser acceptance; existing t_6bebb285 must rerun and begins with a warmed model. Finite serial load does not certify long-duration/concurrent memory safety. OldDEV2c2bcc0 rollback restores known4Gi cold-chat risk. Durable evidence: /opt/data/channels/cuga-delivery/artifacts/t-cdf95beb/handoff.md; no attachments.