Track parcels with 17TRACK

Resolve SKILL_DIR to this skill's installation directory. Use the bundled CLI rather than recreating storage or signature handling. Commands return JSON; non-zero exit status means failure or an incomplete sync.

Setup

Set TRACK17_TOKEN through the host's secret store/environment; never print it. Set TRACK17_DATA_DIR to a private absolute directory outside the repository. Then run:

python3 "$SKILL_DIR/scripts/track17.py" init
python3 "$SKILL_DIR/scripts/track17.py" --help

This revision uses a new local schema. An old database containing packages is rejected without modification. Choose a new data directory, inspect/export the old records locally, and register only the parcels the user still wants. Do not delete the old database or automatically re-register everything: provider quota can be consumed.

Normal workflow

Prefer polling unless push delivery is needed. Read the current parcel list before adding or removing anything. Resolve parcel identity by tracking number plus carrier code, not a guessed local ID.