keisei/KeiSeiKit-1.0
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
KeiSeiKit-1.0/_blocks/stack-swift-spm.md
Parfii-bot 0be354a920 KeiSeiKit-public — clean state 
Single-commit clean baseline after security scrub of niche-tells,
project codenames, internal jargon, and contributor-email leaks.

Contents:
- 100 Rust crates (_primitives/_rust/)
- 37 agent manifests (_manifests/) + generated specs (_generated/)
- 67 user-invocable skills (skills/)
- 33 hooks (hooks/)
- Composition blocks (_blocks/)
- Documentation (docs/, README.md)
- TS adapter packages (_ts_packages/)
- Assembler (_assembler/)
- Roles (_roles/)
- Templates (_templates/)
- Forgejo CI (.forgejo/)

Author: Denis Parfionovich <info@greendragon.info>

License: see LICENSE.
2026-05-01 12:09:03 +08:00

1.5 KiB
Raw Blame History

STACK — Swift SPM executable (macOS)

Use for platform-native macOS UI. Requires some non-obvious incantations to avoid silent failures.

Info.plist embed — each arg prefixed with -Xlinker:

.unsafeFlags([
  "-Xlinker", "-sectcreate",
  "-Xlinker", "__TEXT",
  "-Xlinker", "__info_plist",
  "-Xlinker", "/abs/path/Info.plist",
])

Relative paths silently fail. NSPrincipalClass=NSApplication in Info.plist MANDATORY — without it the binary runs as a console tool, no menubar, no events.

Codesign: codesign --force --sign - <path>/MyApp.app — ad-hoc signature is enough for local use; Gatekeeper flags unsigned .app bundles as damaged.

Menubar lifecycle (mandatory dance):

  1. NSApp.setActivationPolicy(.regular) at launch
  2. Create NSStatusItem via NSStatusBar.system.statusItem(withLength: .variable)
  3. NSApp.setActivationPolicy(.accessory) AFTER status item is attached

Skip any step → icon never appears, no error, silent failure.

Broken / forbidden:

  • MenuBarExtra (SwiftUI) — does NOT work with SPM executables. Use NSStatusItem + SwiftUI popover.
  • Notch overflow (MacBook Pro 14/16 M1+) — new status items hidden behind notch. Verify visibility post-install.

LaunchAgent hygiene (learned from a real disk-bloat incident): a duplicate LaunchAgent or a chatty sync daemon without log-silencing can fill the disk with tens of GB of log chatter. Check launchctl list before adding a LaunchAgent, and keep LaunchAgent stdout/stderr → /dev/null.