Repository navigation
feat(dogfood): automate the five-application evidence loop - #36
Merged
Merged
Conversation
Replaces the manual dogfood_scorecard.md workflow with an in-dashboard 5-application cohort: start a run, confirm real applications as usual, answer one optional feedback question per confirmation, and get an automatic sanitized report with a rule-based go/no-go verdict once the fifth is captured. Reuses existing durable data (job_funnel, assisted_fill_summary, application_preflight, human_interactions) rather than duplicating it; the only new persistence is cohort membership and the operator's own closed-vocabulary feedback, captured atomically inside ConfirmAssistedSubmission's existing transaction so a closed browser or an automatic-pipeline APPLIED transition can never be miscounted. Co-Authored-By: Claude Sonnet 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.
Summary
job_funnel,assisted_fill_summary,application_preflight,human_interactions,GetHumanEffortMetrics's join pattern) rather than duplicating it. The only new persistence is two small tables —dogfood_cohortsanddogfood_cohort_applications— for cohort membership and the operator's own closed-vocabulary feedback (no answer text, no PII).ConfirmAssistedSubmission's existing transaction, so it is atomic with theAPPLIEDwrite: a closed browser, an abandoned session, or the automatic pipeline's separateAPPLIEDpath can never be miscounted.ConfirmAssistedSubmission's signature changes fromerrorto(int, error)to report the capture ordinal back to the caller.documentation/dogfood_scorecard.mdworkflow (left in place as historical record of #545).Fixed two incidental issues found while wiring this in:
cmd/dashboard/main_test.go's hand-rolledapplied_jobsfixture was missingUNIQUE(url), which production has andConfirmAssistedSubmission'sON CONFLICT(url)depends on.cmd/dashboard/schema_upgrade_test.go'sprepareDashboardSchema— a second startup-ensure-list deliberately kept in sync withmain()— was missingEnsureDogfoodSchemaand the new tables in its assertion list.Test plan
gofmt -l ./cmd ./pkg ./internal— cleango build ./...go vet ./...go test ./...— all pass exceptTestServeKnowledgeProfile_KeepsBackupsBoundedAndPrivate, a pre-existing timestamp-collision flake confirmed to fail identically on unmodifiedmainnpm run lint/npm test(85 tests) /npm run buildincmd/dashboard/uiTestDogfoodRun_EndToEnd(start → confirm 5 → feedback → auto-complete → report)🤖 Generated with Claude Code