feat(profile): add practice-area development profile

[ValentinGruener]

Description

Adds the practice-area development profile: developers can see where they stand in each practice area of their workspace, and open an area to understand how that standing came about.

• Server API — a workspace-scoped endpoint deriving the calling developer's standing per area (status, guidance, day-to-day development, feedback provenance), plus area, severity, artifact-kind filtering and severity sorting on the existing observation list. Derivation reuses the existing reflection path (latest run per artifact, quarantine floor, team-hidden repositories excluded) instead of adding a third copy of those rules.
• Profile cards — one card per active area: status badge, a trend hint whose derivation is explained on hover, the guidance sentence, and the pull requests, issues and Slack conversations the assessment rests on.
• Detail page — an assessment-flow diagram showing which practices feed the area and where the developer stands on each, plus a related-activity feed of what Hephaestus observed across every connected integration. Selecting a practice explains why it matters, what good looks like and how it has been developing, and focuses the feed on it. Feed entries carry their source integration, filter by source and severity, sort by date or severity, and expand in place to show the delivered guidance, the reasoning, the evidence, and a link to the reviewed artifact.

The feed deliberately shows raw history including superseded runs — it is an activity monitor, while the status above stays latest-run and quarantine filtered; an info affordance in the section header explains that difference.

Review hint: the three parts are three separate commits (API → cards → detail page), so the diff can be read commit by commit.

How to test

Server — mvn verify -P'!quick' covers PracticeAreaStatusIntegrationTest and ObservationControllerIntegrationTest: status derivation, NO_DATA shape, quarantine floor, cross-workspace isolation, the new filters and severity sorting.

Webapp — pnpm run test:webapp; Storybook (pnpm --filter webapp run storybook) has every state under Components/Profile/PracticeAreaStatusCard and Components/Profile/PracticeAreaDetailPage. The detail page's Overview story is interactive: select practice nodes, filter, sort, expand entries; ManyPractices shows the diagram at ten practices.

In the app — open your own profile in a workspace with practices enabled and completed reviews, then open a card via "See details". The section only renders on the own profile, because the endpoint derives the caller's standing.

Checklist

• Changeset summaries read as user-facing notes (one per user-visible change)
• No operator action required; additive, read-only endpoints
• OpenAPI spec and generated client regenerated and committed

Screenshots

Storybook covers every state; see the two component sections named above.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 5f857c81-6406-410d-83eb-a646040b7ecb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ValentinGruener]

Superseded by stack #1488 — #1486 (server API, spec and generated client) and #1487 (profile surfaces).

The repository adopted stacked pull requests in #1452 after this PR was consolidated, so the reason for carrying all three parts in one PR no longer holds. The work has also been rebased onto current main, which this PR had drifted 20 commits behind, and ported onto the observation vocabulary that #1444 introduced.