Repository navigation
core: Privacy endpoints, setup audits its sign-in, honest 501, mocked modules follow the real session in dev-api (#78) - #85
Merged
Conversation
…t, mocked modules follow the real session (#78) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…TCH writes nothing, mock setup audit rows, 501 without retry, contract text Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the four findings of issue #78, Emily's QA on
make dev-api REAL=core,exposure.Changes
GET/PATCH /core/privacy(modules/core/handlers_privacy.go).privacyViewshows them. Module on/off comes from core's registry. The "configured" facts for flows 3, 10 and 11 come through the nil-safecore.PrivacyFactsport, wired incmd/vedette/wiring.gowith what is true today: AI not configured, default NTP, no OIDC.keyPrivacy/privacySetting). A test proves that a PATCH turns OS update checks off.last_sentis null andpayloadis{}.invalidand change nothing. It is partial: one switch never wipes the other. An empty body writes nothing and audits nothing. Concurrent PATCHes lose nothing.auth.loginaudit row, and the mock's setup writes the same rows in the same order as the backend.TestUsers_TemporaryPasswordSignsInForEveryRole). Steps were requested from Emily on core on dev-api: Privacy page says 'not available', session ends after /setup, temp password from POST /core/users rejected (QA) #78./api/v1/me(web/src/mocks/realSession.ts)./me.VITE_API_MOCK=offbuild.Review
An independent Opus review found 0 Critical and 0 High findings. Everything else is fixed:
/mecache.Its proof tests are now permanent tests.
Deferred (
.ai/deferred/fix-core-qa-78.md), both pre-existing:features/core/logExport.ts.The lead does both in separate PRs.
Local checks
make checkexit 0: Go-race, golangci-lint 0 issues, govulncheck clean, tsc, 27 vitest files / 954 tests. Linux lint 0 issues. main (#80, #83) was merged in afterwards;go vetis clean.Closes #78.
🤖 Generated with Claude Code