TraceRookReal activity is empty
This is expected in the current development preview. Use Explore Demo or launch with --demo to browse sample activity. The foundation service and bridge expose self-tests but do not provide operational live ingestion.
Do not change host settings to make the preview appear integrated. Read the roadmap for the next live acceptance gate.
Anthropic BYOK is unavailable
The current build does not accept API keys or make provider requests. MVP2.5 will add Keychain, consent, validation, budgets, and real analysis.
In the intended live build, a revoked key, network outage, rate limit, unsafe payload, or exhausted budget leaves local rules available with accurate provider status. Replacing a key must not be mistaken for verifying agent hook coverage.
A review notification did not appear
Check TraceRook’s notification permission in system settings and consider Focus mode. Permission should be requested only through an explicit app action. The native sample review remains accessible through Approvals.
The intended service must expire high-risk reviews safely even if delivery fails, the app is not running, or the user never opens the panel. An old notification cannot authorize a later action.
An integration is installed but not verified
In a future live build, distinguish configuration, helper availability, host trust, adapter compatibility, callback receipt, and blocking tests. Codex requires user review of nonmanaged hooks via /hooks. No trust-bypass flag is part of TraceRook setup.
Do not reset or replace entire agent settings to repair one hook. Use a fresh, explicit configuration plan. If a session is idle, verification age may be stale without implying failure.
A source build fails
Confirm Apple Silicon, macOS 26+, Swift 6, and the macOS 27 SDK. Use the checked-in build and test scripts for Command Line Tools environments; Xcode archive validation needs full Xcode.
Known local adjustments include SwiftPM’s native build backend and an SDK 27 State-wrapper compatibility alias when the Command Line Tools installation lacks the macro plugin. These are documented development-tool observations, not waived release requirements.
Useful diagnostic details
A report should include the app and host versions, status code, adapter version, configuration state, trust state, whether a real callback was observed, and sanitized reproduction steps. Never include keys, raw hook payloads, full transcripts, or private source.
Use the source repository to inspect the current implementation record. Local sanitized diagnostic export is an upcoming live feature.