Build secret management pages

[nickbeau]

Detail: Add UI for creating, listing, rotating, and deleting secret descriptors without showing values.

Milestone: Sprint 4: Repository and Secret Management

Source: docs/technical.md sprint plan.

[nickbeau]

I’ve picked this up. I’ve reviewed the issue metadata and timeline; there are no existing issue comments or linked PRs showing in the GitHub issue data. I’m going through the technical docs and current UI/data patterns now, then I’ll implement the secret descriptor management pages with tests and validation before opening a PR.

[nickbeau]

I’m continuing issue #38 from the linked PR #153. I’ve reviewed the issue, the existing issue comment, and PR #153’s metadata, diff, and comments. The PR currently has no review comments, but it is dirty against main; I’m resolving the main-branch integration locally, then I’ll run the build/test/format checks and update the PR.

[nickbeau]

PR #153 has been rebased onto the current main and force-pushed. I resolved the integration by keeping main's existing Data Protection-backed secret store and updating the issue branch to focus on the /settings/secrets UI, docs, and bUnit coverage. Local validation is clean: restore, build with --warnaserror, tests with and without XPlat coverage, format check, docs validation, and a local GET /settings/secrets smoke check all passed.

[nickbeau]

I’ve now reviewed issue #38, linked PR #153, and current branch symphony/38 changes. I’m validating reachability/build/tests and will report status before final PR ready-state updates.

[nickbeau]

I’m continuing from issue #38 + linked PR #153. I’ve pulled issue/PR metadata and comments and will now verify the implementation in the current branch symphony/38, run build/tests/docs checks, add any missing coverage/docs updates, then update issue/PR status before opening for review.

[nickbeau]

I’m continuing validation for issue #38 and PR #153. I’ve reviewed the issue details, existing comments, and linked PR metadata; next I’m checking the current branch against latest main, rerunning build/test/docs validation, and will update the PR if anything needs fixing.