PASS
- Connector settings now persist in a dedicated table and still write audit events.
- Connector state/cursors now persist in a dedicated table with counters, timestamps, failure posture, and restart-safe health.
- Telegram uses
secret_refvalues or the local secret provider instead of raw token settings. - Browser clipper can enforce a local capture token and redacts it before persistence.
- CLI/API/UI/event/source/artifact paths expose configured posture, not secret values.
- Telegram rejected-chat handling, retries, and cursor advancement avoid repeated rejection loops without skipping failed processable items.
- Local folder scans ignore generated/dependency folders and dedupe unchanged files across restart.
/vnextcan update live connector defaults and run connector actions for the current local dogfood loop.- Dogfooding telemetry now includes readiness, trends, review rate, failure causes, scheduler freshness, agent activity, and policy filters.
- Doctor and migration status commands give operators a repeatable local-alpha readiness check.
- New tests and smokes cover connector settings/state, redaction, doctor behavior, and repeatable capture-to-brief behavior.
- none for this dogfood hardening scope
- none blocking
- the local encrypted secret file is an alpha fallback; production use should connect the same interface to OS keychain or managed secret infrastructure
- moderate for vNext connector flows because settings/state moved from event-log-only fallback to dedicated storage
- moderate for
/vnextbecause connector configuration now performs live writes when local API/user config is present - covered by unit tests, integration tests, web lint/build, migration status, connector-hardening smoke, secret-redaction smoke, dogfood-doctor smoke, live-capture smoke, capture-to-brief smoke, agentic-scheduler smoke, and evals
- none blocking after final docs/control truth check rerun
- no
- yes, updated vNext architecture to include dedicated connector settings/state storage, local secret references, and connector cursor reliability
- rerun final verification after docs edits
- commit, push, open PR, wait for checks, squash-merge, and delete the branch