[ffi] Evaluate shellout or child_process and isolate command-tooling FFI #20

Activity

1. GG-O-BP

   added this to the FFI reduction 3: Platform adapter evaluation milestone on Sep 7, 2026
2. GG-O-BP

   added

   ffiForeign-function interface boundaries and interopForeign-function interface boundaries and interop

   refactorInternal restructuring without an intended feature changeInternal restructuring without an intended feature change

   spikeTime-boxed investigation needed before implementationTime-boxed investigation needed before implementation

   on Sep 7, 2026
3. GG-O-BP commented on Sep 7, 2026

   

   GG-O-BP

   on Sep 7, 2026

   CollaboratorAuthor

   More actions

   분석 결과, generic exec에는 shellout을 채택하고 Glendix 전용 프로세스 코드는 유지하는 하이브리드 분리가 적합합니다.

   • shellout.command는 JavaScript/Node에서 동기식 spawnSync 기반이며, exit status를 Result로 돌려주고 LetBeStdout/LetBeStderr로 현재의 inherited stdio 동작을 보존할 수 있습니다.
   • 다만 현재 cmd.exec 공개 API는 인수 배열이 아니라 shell command string을 받으므로, Unix의 /bin/sh -c와 Windows의 ComSpec /d /s /c로 변환하는 얇은 플랫폼 경계가 필요합니다.
   • plinth/node/child_process의 현재 API는 exec/spawn handle과 stdin/kill만 제공하며, 동기 완료 결과, exit code, stdout/stderr 정책을 typed Result로 제공하지 않아 이 primitive의 대체재로는 부족합니다.
   • gleam ... 실행 시 Erlang backend의 알려진 불필요 warning만 제거하는 기존 동작은 shellout이 stdout/stderr를 분리해 필터링하는 API를 제공하지 않으므로 작은 custom boundary로 남겨야 합니다. 이는 generic execution이 아니라 Glendix의 Gleam build-output 정책입니다.
   • bridge 생성/정리, dev watcher, experimental-native 환경 및 Node/npm shim, Rollup/WASM 처리는 이 이슈의 non-goal이며 기존 custom tooling으로 유지합니다.

   구현 시 다음 계약을 보존하겠습니다.

   1. cmd.exec(command:) -> Result(Nil, CommandError) 공개 signature와 동기 동작
   2. 성공 시 Ok(Nil), 실패 시 CommandFailed("execute command", reason)
   3. stdin/stdout/stderr inherited 동작과 shell string 해석
   4. Gleam warning filtering 및 실패 메시지(Command failed: <command>) surfacing
   5. bridge/native tooling의 기존 semantics와 cleanup
   6. glendix -> mendraw의 현재 Hex dependency source

   테스트는 generic command 성공/실패, shell-string 처리, 실패 reason surfacing, Gleam filtered-runner 성공/실패를 contract 수준에서 추가하고 FFI declaration/export gate까지 실행하겠습니다.
4. GG-O-BP

   closed this as completedin #34on Sep 7, 2026
5. GG-O-BP

   added a commit that references this issue on Sep 7, 2026

   Merge pull request #34 from glendix-labs/refactor/shellout-command-is…

   ...

   This issue will close once commit 0bf413d is merged into the 'main' branch.

   0bf413d
6. GG-O-BP commented on Sep 7, 2026

   

   GG-O-BP

   on Sep 7, 2026

   CollaboratorAuthor

   More actions

   ✅ Resolved via #34, merged into main (merge commit 0bf413d, implementation commit 0b1aa55).

   What shipped

   • Generic cmd.exec now delegates to the maintained shellout ~> 1.8.0 synchronous command, replacing the bespoke shell FFI wrapper while keeping the public contract stable (cmd.exec(command:) -> Result(Nil, CommandError), CommandFailed("execute command", reason)).
   • Cross-platform shell semantics preserved (Unix /bin/sh -c, Windows ComSpec /d /s /c).
   • New focused glendix/command module (+ FFI) with a contract test asserting the shellout.LetBeStdout SIGINT listener is cleaned up after execution.
   • plinth/node/child_process was evaluated and rejected (no synchronous completion / typed exit status / typed stdio). The remaining small custom FFI (Gleam warning filtering) is retained and documented in the READMEs.

   Verification

   • Family-wide ./scripts/verify.sh final passed: source/style/FFI/boundary gates, all standalone consumers, all package tests (gleam test 142 passed), Glendam browser checks, widget .mpk build, and Mendix full E2E (BUILD SUCCEEDED + post-boot browser smoke).
   • package-gates CI on the PR passed.
   • Dependency contract preserved: glendix -> mendraw remains a Hex requirement; pushed-tip dependency check passed.