mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-19 10:33:29 +00:00
ed58890471
The previous layout put AddressProbeStep at the top with the agent card below as "Or install the agent on the host." Both sections read as alternatives to the probe, which made the probe the primary action even though the probe is inherently a Platform-API-oriented move (figure out which API to connect to). A user committed to the agent path has no use for it. The "Recommended" chip on the agent card did not fix this — the structural lead won. Move the agent card to the top of the Add landing with no divider above it (it's the primary, not an alternative). Fold the probe + platform grid into a single "Or connect a platform API directly" section below, so the ordering matches the story: agent first, API as fallback for hosts the agent can't cover. Architecture pin in settingsArchitecture.test.ts updated to guard the new ordering: agent card copy indexOf < API section indexOf < probe indexOf. Explicitly asserts the old "Or install the agent on the host" divider is gone. |
||
|---|---|---|
| .. | ||
| public | ||
| scripts | ||
| src | ||
| .bundlesize.json | ||
| .gitignore | ||
| .jscpd.json | ||
| .prettierignore | ||
| .prettierrc | ||
| DESIGN_SYSTEM.md | ||
| eslint.config.js | ||
| hosts-tab.txt | ||
| index.html | ||
| package-lock.json | ||
| package.json | ||
| pnpm-lock.yaml | ||
| postcss.config.js | ||
| tailwind.config.js | ||
| ThresholdsTableTop.txt | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| update_skeletons.cjs | ||
| update_sparkline.cjs | ||
| update_sparkline.js | ||
| update_sparkline_size.cjs | ||
| vite.config.ts | ||