chore: surface token when applying auth, allow named secret creation

[usman-khalid]

Updates Site Admin tool to:

• allow creation of named secrets
• surface the token when applying authentication to a site
• fix some styling for dark mode

Test URLs:

• Before: https://main--helix-tools-website--adobe.aem.live/tools/site-admin/index.html
• After: https://auth--helix-tools-website--adobe.aem.live/tools/site-admin/index.html

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

• Re-run PSI checks
• Re-sync branch

Commits

• bbdade2 ✅ (latest)
• 7e4be0a ✅
• 1071620 ✅

[aem-code-sync]

	Page	Scores	Audits	Google
📱	/tools/site-admin/index.html
🖥️	/tools/site-admin/index.html

[claude]

SHOULD FIX: Secret value input should use type="password" to mask the value on screen.

The auth token display in the same PR correctly uses type="password". Per AGENTS.md: Consider that everything you do is client-side code served on the public web.

Suggested change

	<label for="secret-value">Value (optional)</label>
	<input type="password" id="secret-value" placeholder="e.g. secret from external service" />

[claude]

Code Review Summary

Issues Found

SHOULD FIX:

• tools/site-admin/helpers/modals.js — Secret value input for named secret creation uses type="text" instead of type="password", exposing the value in plaintext on screen. The auth token display added in this same PR correctly uses type="password". (AGENTS.md security)

One-Click Fixes

I have added a GitHub Suggestion for the fixable issue. Go to Files changed and click Commit suggestion to apply.

Verdict

COMMENT — one security hygiene fix recommended before merge.