FE-1532: Track a launch config for the Petrinaut dev servers

[kube]

🌟 What is the purpose of this PR?

Tracks a launch configuration for the Petrinaut dev servers, so agent sessions start them by name instead of rediscovering commands and ports. Stacked on #9390.

🔗 Related links

• FE-1532 (internal)

🔍 What does this change?

• Adds .claude/launch.json with three environments, named by package: the @hashintel/petrinaut Storybook, the @apps/petrinaut-website demo app, and @apps/petrinaut-docs.
• The docs entry runs through Turborepo so the architecture-docs bundle regenerates before the site serves.

Pre-Merge Checklist 🚀

🚢 Has this modified a publishable library?

This PR:

• does not modify any publishable blocks or libraries, or modifications do not need publishing

📜 Does this require a change to the docs?

The changes in this PR:

• are internal and do not require a docs change

🕸️ Does this require a change to the Turbo Graph?

The changes in this PR:

• do not affect the execution graph

🐾 Next steps

• A fourth entry, petrinaut-optimization, runs the full local optimization loop (browser → Vite proxy → petrinaut-opt service → petrinaut CLI subprocess) and was verified end to end on 2026-08-28. It is held out of this PR because its --port 5175 --strictPort arguments only reach Vite with two commits from FE-1529: Document the local optimizer loop #9388 ("Forward extra arguments to Vite in the optimization launcher", "Reuse an optimizer already serving on the port"), and FE-1529: Document the local optimizer loop #9388 is a draft stacked behind FE-1518. Without them the declared port never opens and the preview hangs. Add once FE-1529: Document the local optimizer loop #9388 lands:

  {
    "name": "petrinaut-optimization",
    "runtimeExecutable": "yarn",
    "runtimeArgs": ["dev:petrinaut-optimization", "--port", "5175", "--strictPort"],
    "port": 5175
  }

  Notes for that entry: Docker must be running and the first launch builds the image; a stale long-lived optimizer container answers the run route with 404, so stop it and let the launcher start a fresh one; the optimizer demo lives at the /optimization route (launch.json localhost urls are origin-only); the loop is documented in the "Running the loop locally" arch-docs page FE-1529: Document the local optimizer loop #9388 adds.

🛡 What tests cover this?

• None. The file is configuration read by Claude Code.

❓ How to test this?

1. Check out the branch in a Claude Code session in this repo.
2. Ask for a preview of one of the three environments and confirm the server starts from the named configuration on its declared port.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hash	Ready	Preview	Aug 29, 2026 2:04pm
petrinaut	Ready	Preview	Aug 29, 2026 2:04pm
petrinaut-docs	Ready	Preview	Aug 29, 2026 2:04pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
hashdotdesign-tokens	Ignored	Preview	Aug 29, 2026 2:04pm

[cursor]

PR Summary

Low Risk
Developer-only Claude Code configuration with no runtime, library, or Turbo graph impact.

Overview
Adds .claude/launch.json so Claude Code can start Petrinaut local previews by name instead of rediscovering yarn commands and ports.

The file defines three version 0.0.1 configurations: Storybook for @hashintel/petrinaut on port 6006, the demo site @apps/petrinaut-website on 5173, and docs @apps/petrinaut-docs on 4321 (docs dev runs via turbo with --filter so architecture docs regenerate before serve). A fourth optimization loop entry is intentionally deferred until stacked PR #9388 forwards Vite port flags correctly.

^{Reviewed by Cursor Bugbot for commit 441e013. Bugbot is set up for automated code reviews on this repo. Configure here.}