Align auth restart guidance with managed dev runtime

This commit is contained in:
rcourtman 2026-03-24 15:42:22 +00:00
parent 1b1900e8bb
commit 0f32d5b079
3 changed files with 9 additions and 4 deletions

View file

@ -258,6 +258,11 @@ of allowing plaintext licensing state to remain on the runtime primary path.
That same shared token-settings boundary must stay under explicit proof routing
on both sides: `frontend-modern/src/components/Settings/APITokenManager.tsx`,
`frontend-modern/src/components/Settings/apiTokenManagerModel.ts`, and
That same security settings presentation boundary also owns deployment-specific
restart guidance after auth changes. When `securityAuthPresentation.ts`
describes the development deployment, it must point at the canonical managed
runtime control surface (`npm run dev:restart` from the repo root), not a
stale `pulse-hot-dev` service name or any lane-local restart folklore.
`frontend-modern/src/components/Settings/useAPITokenManagerState.ts` must
continue to carry the direct `security-settings-surfaces` proof path together
with the API-contract token-management proof instead of borrowing coverage only

View file

@ -36,8 +36,8 @@ describe('securityAuthPresentation', () => {
command: 'systemctl restart pulse',
});
expect(getSecurityAuthRestartInstruction('development')).toEqual({
label: 'Restart the development server:',
command: 'sudo systemctl restart pulse-hot-dev',
label: 'Restart the managed development runtime from the repo root:',
command: 'npm run dev:restart',
});
expect(getSecurityAuthRestartInstruction()).toEqual({
label: 'Restart Pulse using your deployment method',

View file

@ -45,8 +45,8 @@ export function getSecurityAuthRestartInstruction(
};
case 'development':
return {
label: 'Restart the development server:',
command: 'sudo systemctl restart pulse-hot-dev',
label: 'Restart the managed development runtime from the repo root:',
command: 'npm run dev:restart',
};
default:
return {