Some checks failed
ci / Validate workspace (push) Successful in 12m32s
landing-page-ci / Validate landing page (push) Successful in 9m41s
landing-page-deploy / Deploy landing page (push) Failing after 5m23s
github-metrics / Generate repository metrics SVG (push) Failing after 2m3s
refresh-contributors-wall / Refresh contributors wall cache bust (push) Failing after 11s
This repository contains the open-design daemon CLI source code, built and packaged at https://helix-mind.ai/cli/open-design/latest.tgz for use by the HelixMind /design slash command. Licenses: Apache-2.0 (root) + MIT (skills/*)
2.0 KiB
2.0 KiB
tools/pack
Follow the root AGENTS.md and tools/AGENTS.md first. This tool owns the repo-external packaged build/start/stop/logs command surface.
Owns
- Local packaging orchestration for packaged Open Design artifacts.
- mac build/install/start/stop/logs/uninstall/cleanup smoke commands.
- Windows NSIS build/install/start/stop/logs/uninstall/cleanup/list/reset smoke commands.
- Windows registry observation/cleanup must go through
reg.exeand stay scoped to entries matching the namespace install/uninstaller paths. - Windows lifecycle logs must expose NSIS automation logs/markers/timings in addition to app runtime logs.
- Linux AppImage build/install/start/stop/logs/uninstall/cleanup smoke commands.
- Linux containerized builds via
electronuserland/builderDocker image for distro-agnostic glibc compat. - Consuming sidecar/process/path primitives from
@open-design/sidecar-proto,@open-design/sidecar, and@open-design/platform.
Does not own
- Product business logic.
- Sidecar protocol definitions.
- A second process identity model.
- Product/business update runtime integration.
Rules
- Do not hand-build
--od-stamp-*args; usecreateProcessStampArgswithOPEN_DESIGN_SIDECAR_CONTRACT. - Do not use port numbers in data/log/runtime/cache path decisions. Namespace decides paths; ports are only transient transports.
- Release artifacts keep canonical app identity (
Open Design.appon mac,Open Design.exeinside the Windows installer); local tools-pack installs may use namespace-scoped install paths only as a developer multi-instance validation convention. - Do not let namespace-named
.appinstalls change data/log/runtime/cache path conventions. - Use
--portablefor public/release artifacts so packaged config does not bake local tools-pack runtime roots from the build machine. - Pack resource files used by electron-builder belong under
tools/pack/resources/; do not point pack logic at Downloads, web public assets, docs assets, or other app-owned resource paths.