Nicolas Cantu
ca03324838
**Motivations:** - Keep the Lapce fork changes replayable via patch files in the monorepo. - Expose a minimal Smart IDE cockpit UX (agents, runs, services, connection) inside Lapce. **Root causes:** - N/A **Correctifs:** - ia-dev-gateway: parse YAML frontmatter (name/description) from agent markdown files. **Evolutions:** - Export new Lapce patch files for the Smart IDE panel + connection helpers. - Add documentation for the Smart IDE panel. **Pages affectées:** - N/A
Lapce patches (Smart IDE)
This folder versions the Smart IDE modifications applied to Lapce.
Why this exists:
- The Lapce checkout lives in
core_ide/(and is ignored by the parentsmart_idegit repository). - We still want a reviewable, replayable history of the core editor changes.
Files
series: ordered list of patch filenames to apply (one per line,#comments allowed).*.patch:git format-patchoutput generated fromcore_ide/.
Workflow
Apply patches to core_ide/
From the smart_ide repo root:
./scripts/core-ide-apply-patches.sh
Export patches from core_ide/
- Make commits inside
core_ide/(in a dedicated branch, e.g.smart-ide). - Export the patch series:
./scripts/core-ide-export-patches.sh
This regenerates patches/lapce/*.patch and rewrites patches/lapce/series.
Remotes
Recommended convention inside core_ide/:
upstream: official Lapce (https://github.com/lapce/lapce.git)origin: internal fork (team forge)
Use ./scripts/ensure-core-ide.sh --fork-url <...> to set this up.