# Weekly Command Center

A small, portable macOS launcher for your weekly planning stack. Double-click the
applet to run your own planning script. No subscription, dependencies, or startup
screen. Successful launches are silent; missing scripts and script failures show
a clear dialog.

This is a launcher template, not the author's personal planning dashboard. The
included launch script is intentionally a no-op until you add your own logic.

## Folder layout

```text
Weekly-Command-Center/
├── Weekly Command Center.app/
├── Weekly Command Center.applescript
├── scripts/
│   ├── launch.sh
│   └── grocery.sh
├── README.md
├── WORKSHOP.html
└── LICENSE
```

## Install

1. Unzip the entire folder anywhere on your Mac. Keep `scripts` beside the `.app`.
2. Edit `scripts/launch.sh` in a text editor and add your weekly planning steps.
3. Double-click `Weekly Command Center.app`. Moving the whole folder is safe;
   moving just the app requires bundling the scripts or setting the override below.

macOS may ask you to authorize an unsigned downloaded app. Use Finder's Open
action or the explicit Open Anyway control in Privacy & Security if offered.
Do not disable Gatekeeper globally. You can also compile the reviewed source on
your own Mac using Apple's included tools.

## Compile from source

In Terminal, change into this folder and run:

```sh
chmod +x scripts/launch.sh scripts/grocery.sh
osacompile -o 'Weekly Command Center.app' 'Weekly Command Center.applescript'
```

Or open the `.applescript` in Script Editor, choose File → Export, select
Application, and leave both **Stay open after run handler** and **Show startup
screen** unchecked. To distribute one self-contained app, copy `scripts/` into
`Weekly Command Center.app/Contents/Resources/` after compilation.

## Use a different launch script

Resolution order:

1. `WCC_LAUNCH_SCRIPT` in the app's environment, or the GUI login-session value.
2. `scripts/launch.sh` beside the app.
3. `Contents/Resources/scripts/launch.sh` inside the app bundle.

The override must point to a readable file; an invalid override shows an error
instead of silently running a different script. Paths containing spaces or
apostrophes are supported. Use a fully expanded path, not a literal `~`.

For Finder launches:

```sh
launchctl setenv WCC_LAUNCH_SCRIPT "$HOME/my-planning/scripts/launch.sh"
```

Quit the app before opening it again. This setting is for the current login
session; it is not a permanent system setting. Remove the override with:

```sh
launchctl unsetenv WCC_LAUNCH_SCRIPT
```

For a direct Terminal source run:

```sh
WCC_LAUNCH_SCRIPT="$HOME/my-planning/scripts/launch.sh" \
  osascript 'Weekly Command Center.applescript'
```

An `export` in Terminal alone does not change Finder's environment. Finder also
has a minimal PATH: use full executable paths or set PATH in your custom script
for tools you install separately.

## Customize and connect

Put your steps in the marked section of `scripts/launch.sh`. It uses
`set -euo pipefail` and resolves its own directory, so the caller's working
directory does not matter. Start persistent services in the background with
their output redirected, and check readiness before returning. A nonzero script
exit is displayed by the applet; the applet cannot detect failures in detached
jobs after the launch script exits.

The optional `scripts/grocery.sh` is an empty integration hook. Enable it by
setting `WCC_RUN_GROCERY=1` in your environment or inside `launch.sh`. Future
grocery lists or family automations can use this hook; none are implemented or
connected by this template.

## Share

Zip the whole folder with the app and scripts together. Source is included so
recipients can inspect and recompile it. A broadly distributed signed app would
need your own Apple Developer signing identity and notarization; this package
is unsigned. macOS only. Free to use and modify under the MIT license.