feat(db): add example values to all protobuf schemas

[cooper (czxtm)]

Summary

• Adds example values to every field across the 18 protobuf schemas that were missing them (apps, aws, config, databases, deployment, extensions, files, healthchecks, modules, onboarding, scripts, secrets, services, shells, sst, step-ca, tasks, variables).
• Plumbs examples through the existing buf-gen pipeline: proto.nix now appends (example: ...) to each field's proto comment, with strings JSON-escaped so embedded quotes/newlines don't break proto3 syntax. protobuf-ts carries those comments through to TypeScript JSDoc, so the studio (and any consumer of the generated .d.ts) gets examples for free — no separate fixtures pipeline.
• Adds apps/web/scripts/demo-smoke.ts — a standalone Bun smoke test that drives the studio's MSW-backed demo agent directly and verifies /health, /api/state, /api/nix/data?entity=apps, and /api/process-compose/processes return the expected fixture data.

Why

The studio panels and forms benefit from realistic placeholder values, and the protonix schema is the natural place to author them once and have them flow to TS, Go, and JSON Schema outputs together. Threading them through the existing .proto comment path means we don't introduce a new generation pipeline or proto extension — buf generate already preserves comments as JSDoc.

Reviewer notes

• The apps/stackpanel-go/internal/agent/server/connect_entities_gen.go diff is a reordering of generated handler methods (it falls out of buf generate after the proto regeneration) and contains no semantic changes.
• The pre-existing theme.proto.nix schema already used the new proto.mkField-style example = ...; the new schemas use the legacy positional API via proto.withExample since most schemas in the codebase use that style. Both APIs converge in proto.mkField and produce identical proto output.
• Example values are not part of the proto wire format and only show up in comments; no changes to message shapes or field numbers.

Test plan

• bash packages/proto/generate.sh proto — all 26 protos regenerate cleanly, (example: ...) annotations present
• buf generate (in packages/proto/) — succeeds, examples flow into packages/proto/gen/ts/*_pb.d.ts JSDoc
• bun apps/web/scripts/demo-smoke.ts — 11/11 assertions pass against the demo agent's MSW handlers
• Visual smoke test of /demo route in the studio (manual)

🤖 Generated with Claude Code

[cursor]

PR Summary

Medium Risk
Mostly comment/metadata plumbing, but it touches code generation outputs and adds/reshuffles agent RPC handlers, so mismatches between generated clients/servers or entity names could cause runtime integration issues.

Overview
Adds field-level example annotations across the Nix-defined protobuf schemas and updates proto.nix rendering to append (example: ...) to field comments with proper escaping so examples flow through generated artifacts.

Regenerates Go protobuf bindings to include these examples in doc comments (and adds a new optional description field accessor on EnvironmentVariable), and adds apps/web/scripts/demo-smoke.ts, a Bun script that exercises the demo agent MSW handlers for key endpoints. The connect_entities_gen.go changes are generated method reordering plus new Get/SetSecrets and Get/SetAws handlers in the expected entity map.

^{Reviewed by Cursor Bugbot for commit e055f9c. Configure here.}

[github-actions]

Preview deployed to pr-23 — https://pr-23.stackpanel.com

[github-actions]

Docs preview deployed to pr-23

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is ON. A cloud agent has been kicked off to fix the reported issue. You can view the agent here.}

^{Reviewed by Cursor Bugbot for commit e055f9c. Configure here.}

[cursor]

Undocumented protobuf message shape change in EnvironmentVariable

Medium Severity

The proto regeneration adds a new Description field (proto field 7, oneOf index 3) to the EnvironmentVariable Go struct and raw descriptor. The old generated code only had fields 1–6; now field 7 is materialized with a new GetDescription() accessor and an updated rawDesc. This is a real protobuf wire-format and JSON-serialization change — not just a comment update — despite the PR description explicitly claiming "no changes to message shapes or field numbers." Consumers deserializing EnvironmentVariable will now see a description key in JSON output when set, which could break snapshot tests or downstream expectations.

Additional Locations (2)

• packages/proto/gen/gopb/apps.pb.go#L452-L458
• packages/proto/gen/gopb/apps.pb.go#L510-L523

 

^{Reviewed by Cursor Bugbot for commit e055f9c. Configure here.}

[cursor]

Bugbot Autofix determined this is a false positive.

Comparing this branch to its base shows no diff in packages/proto/gen/gopb/apps.pb.go, and EnvironmentVariable.description already exists in both, so this PR does not introduce the reported message-shape change.

_{You can send follow-ups to the cloud agent here.}