[TeoSlayer]

Do not merge. Merging a submission publishes it: publish-on-merge.yml runs scripts/publish-submission.sh for every changed submission.json on main. This app stays unlisted until DoorDash agrees to the listing (see Terms).

What it is

io.pilot.doordash 0.2.5 is a thin cli adapter over the user's own DoorDash CLI (dd-cli 0.2.5, DoorDash's waitlist-only beta), signed in to the user's own DoorDash account.

• doordash.exec: verbatim argv to dd-cli (the whole tool), plus optional stdin.
• doordash.cli_help: dd-cli --help, no sign-in needed.
• doordash.version: dd-cli --version, no sign-in needed.

It does not ship dd-cli. The user installs it with DoorDash's get-started guide and runs dd-cli login once.

It is marked Beta in the display name, tagline, description and store page. The store page links the get-started guide and states the waitlist, the platforms (macOS Apple Silicon and Linux x86_64 only), the personal-use terms, that checkout charges a real card (possibly with no confirmation step), and that the app is not affiliated with DoorDash. The manifest grants only proc.exec dd-cli, fs.read $APP/config.json and audit.log.

Terms (why this is a draft)

• DoorDash's CLI Access Terms ship as LICENSE.txt in every dd-cli release. They allow personal, non-commercial use, including by the user's own agents (section 5). They also say: "You may not use the CLI to … (b) build, offer, operate, or monetize any product, service, or platform that relies on CLI access" (4.1). The license is "non-transferable, non-sublicensable" (11.1), so dd-cli can't be redistributed.
• DoorDash's MCP, its organization product, "is not currently available to be integrated into consumer-facing products" (About DoorDash MCP).
• The CLI terms name legal@doordash.com for questions.

Depends on

• scaffold: cli apps find a user-installed CLI outside the daemon's PATH #128. The daemon runs under launchd with PATH=/usr/bin:/bin:/usr/sbin:/sbin, and DoorDash's installer puts dd-cli in ~/.local/bin. Without scaffold: cli apps find a user-installed CLI outside the daemon's PATH #128 the app can't find dd-cli on a standard macOS install. This branch is stacked on scaffold: cli apps find a user-installed CLI outside the daemon's PATH #128's commit.

Validated

• pilot-app verify-submission: all four platforms build, pin, sign and verify.
• TestAllSubmissionDemosValid, TestAllSubmissionNextStepsValid, TestSubmissionGatewaysAreReachable, TestSubmissionCrossAppStepsResolve: pass. demo-score: 100.
• Socket mode on macOS arm64, against DoorDash's real dd-cli 0.2.5 (release checksum verified) installed the way its installer does it (~/.local/bin/dd-cli + _internal/), with the adapter on launchd's PATH. Every method was called, and each matches running dd-cli directly:
  • version → dd-cli, version 0.2.5
  • cli_help / exec ["--help"] → root help
  • exec ["search","--help"] while not signed in → exit 1, "missing credentials". dd-cli gates even command help behind sign-in.
  • dd-cli not installed → executable file not found, which the next-steps edge matches.

Not validated yet

• Anything signed in (search, menu, cart, order, checkout). That needs a DoorDash account approved off the waitlist. The command flags and the --intent format are therefore not checked: the demo shows --help navigation, as DoorDash's own skill recommends, rather than guessed flags.
• Linux (Docker was stopped) and a real pilotctl appstore install.
• No publisher key yet. Generate one when this is cleared for listing, and back it up; every future version must use the same key.

🤖 Generated with Claude Code