Merge pull request #16 from dekaruntime/fix/next-steps-deka-dev

Revert next-steps command to deka dev

Revert next-steps command to deka dev, not a package-manager idiom

PR #13 replaced deka dev in the scaffolder's final output with each package manager's own idiom for running the "dev" script (npm run dev, pnpm dev, etc.), on the premise that a bare deka dev can't run without a global install. That premise was wrong: deka from @dekaruntime/deka is scoped to the project, and Sami's own bug report showed deka dev running and reaching a compile error, not "command not found".

Keep the real fix from#13 -- the missing cd <dirName> line, deka init invoked from the parent directory, and suppression of deka init's own next-steps block so only one prints -- and restore the deka dev command underneath it, unconditionally on package manager. Also drops runScript from package-manager.js, now dead code with no other callers.

-claude

Claude-Session: https://claude.ai/code/session_01XHuN9xFKcoJaoTJfBwxsb1

Merge pull request #15 from dekaruntime/fix/e2e-macos-realpath

fix(test): compare realpath'd cwd in the e2e assertion

fix(test): compare realpath'd cwd in the e2e assertion

macOS resolves /var -> /private/var, so the spawned process reports a realpath'd cwd while the test compared the raw mkdtemp path. The assertion failed on every macOS run and passed on Linux CI -- which is how 0.0.5 shipped with a red suite locally and green CI.

Compares command and cwd separately, with both sides realpath'd, so it still fails if init is invoked without the directory argument or from the wrong directory.

Claude-Session: https://claude.ai/code/session_01XHuN9xFKcoJaoTJfBwxsb1

Merge pull request #14 from dekaruntime/release/0.0.5

release: create-deka-app 0.0.5

release: create-deka-app 0.0.5 (next steps tell you to cd)

Claude-Session: https://claude.ai/code/session_01XHuN9xFKcoJaoTJfBwxsb1

Merge pull request #13 from dekaruntime/fix/next-steps-cd

Fix missing cd instruction in first-run next steps

Fix missing cd instruction in first-run next steps

create-deka-app ran deka init with cwd set to the new project directory and no positional argument, so deka's next-steps text never printed a cd <dir> line -- correct advice for deka init myapp typed by hand, wrong for us. It also suggested a bare deka dev/deka serve, which isn't on PATH since deka only lives in the new project's node_modules/.bin.

Now invoke deka init <dirName> from the parent directory (deka never overwrites the package.json already written there), and suppress deka's own next-steps block in favor of create-deka-app's own: a cd <dirName> line plus the detected package manager's own idiom for running the "dev" script (npm run dev / pnpm dev / yarn dev / bun run dev), which works with nothing beyond what the install step already put on disk.

Verified against the real deka binary (v0.53.2) directly, not just the test stub -- see PR description for the revert-and-run proof.

Claude-Session: https://claude.ai/code/session_01XHuN9xFKcoJaoTJfBwxsb1

Merge pull request #12 from dekaruntime/release/0.0.4

release: create-deka-app 0.0.4

release: create-deka-app 0.0.4 (runtime version pin fix)

Claude-Session: https://claude.ai/code/session_01XHuN9xFKcoJaoTJfBwxsb1