apm init does not create start.prompt.md, causing apm run start to fail immediately

[edenfunf]

Bug Report

Description

After running apm init, the next advertised step is apm run start, but this fails immediately because start.prompt.md does not exist. The "Next Steps" panel also lists apm install and apm compile as if they are required, but neither is needed for a basic first run.

Steps to Reproduce

mkdir my-project && cd my-project
apm init --yes
apm run start

Result: apm run start exits with an error — no prompt file found.

Expected Behavior

apm init should create a starter start.prompt.md so the end-to-end flow (init → run) works without additional steps. The "Next Steps" guidance should reflect what a new user actually needs to do.

Root Cause

_create_minimal_apm_yml() in _helpers.py writes only apm.yml. There is no code path that creates start.prompt.md, so the file is absent after init.

The "Next Steps" list includes:

• apm install <owner>/<repo> — not required to run a basic prompt
• apm compile — not required unless skills/instructions are installed

These mislead new users into running unnecessary commands before apm run start.

Environment

• OS: Windows 11
• APM version: current main
• Python: 3.13

Proposed Fix

• Create start.prompt.md in _create_minimal_apm_yml() when plugin=False, skipping if the file already exists (so re-running apm init on an existing project is safe)
• Trim next-steps to the three essential actions: install runtime → edit prompt → run
• List start.prompt.md in the "Created Files" table shown after init

[edenfunf]

Closing this — I realized I had already filed and submitted a fix for this in PR #606 back on 2026-04-07 and forgot about it. Sorry for the duplicate.