CodeNomad/dev-docs/INDEX.md
Pascal André 1f91a64020
ci: serve release downloads from verified dev-seeded caches (#1390)
ci: serve release downloads from verified dev-seeded caches

github.com release downloads returned 502/504 intermittently for hours on 2026-11-08, failing "Install the Electron binary" in test and build jobs on every OS and Tauri bundling (AppImage runtime, Windows installer tooling). Every job re-downloaded these artifacts on each run.

A trusted seeding workflow (push to dev on lockfile/cache changes, twice-weekly schedule, manual dispatch; dev only, contents: read) fills dev-scoped caches for the four runner images: npm, Electron zips and electron-builder's fpm/winCodeSign, Cargo's downloaded crates and the AppImage runtime. Tauri bundler tools are saved only by the scheduled nightly dev build. A restore-only composite action re-verifies what a tool would otherwise trust: Electron zips against electron's checksums.json before app-builder sees them, .crate files against Cargo.lock, and the AppImage runtime against GitHub's published SHA-256. Pull-request and test-signing workflows declare cache-mode: read, so they restore but never create caches; this also stops the per-PR npm cache copies that pushed the repository over its 10 GB cache limit. Cargo target/ is deliberately not cached.

On a cache miss or helper failure every tool downloads exactly as before; no retry hides real failures, and no test, signing or verification step changes. Restore steps are skipped when a checked-out branch lacks the new action, so open PRs keep today's behaviour until they merge dev.

New download-cache tests (guards, ordering, restore-only, save conditions, verification) and the existing workflow/policy tests pass (55/55); strict YAML and actionlint are clean apart from actionlint's missing cache-mode support. Independent review found no findings.
2026-11-08 18:03:18 +01:00

5.6 KiB

Documentation Index

Start with README for installation and usage, then architecture for ownership boundaries and code locations. AGENTS.md defines the rules that apply everywhere (styling, i18n, contribution) and indexes the area documents whose rules bind each area.

Runtime and ownership

History and pruning

UI and extensions

  • UI conventions: dialogs, utility windows, icon toggles, surfaces and scrollbars.
  • Application shell: panel toggles, drawers, tabs, session sidebar and native menus.
  • Composer: context selectors, height, focus, delivery, attachments and mentions.
  • Transcript rendering: Message content presets, token lines, tool renderers and lifecycle signals.
  • Settings and Preferences: settings rows, the Preferences window, Providers/Web search, Stats and notifications.
  • Projects and tabs: closing tabs, temporary workspaces, the new-instance launcher and Git-unavailable mode.
  • Public user help: multilingual static site, stable anchors, local search, app entry points and Pages validation.
  • Files panel: workspace editing, Git changes/history and preview lifecycle.
  • Questions and permissions: permissions/Forms dock, drafts and pending-request recovery.
  • Keyboard shortcuts: the shortcut catalog, recording and dispatch.
  • Provider accounts: native account selection, usage credentials and bounded quota/rotation policy.
  • Plugin controls: adding and removing plugin sources, explicit Global/Project activation, versions and native package check/update.
  • OpenCode integrations: the integration marker, catalog and RPC contract, its parity with the vendored specification, and the fake registry and integration fixtures.
  • Panel extensions: distribution, trust, consent and sandbox/API boundaries.
  • Palette sources: color provenance and validation.

Missions

Desktop automation and validation