Repository navigation
Align trust evidence, signup recovery and MCP outcome metrics - #60
Merged
Merged
Conversation
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
Published packages no longer imply signed or evaluated releases. Show current-version signing/evaluation metadata separately from aggregate trust, improve weak-password recovery while retaining backend rejection, and count MCP outcomes only after inspecting the result.
The first commit contains mechanical lint formatting; the second contains behavior, tests and validation tooling. Regenerated artifacts stay synchronized in the automatic version-bump workflow. A follow-up commit patches TanStack Start to 1.168.60, DOMPurify to 3.4.17 and launch-editor to 2.14.2 in both lockfiles; the dependency audit now blocks high/critical findings.
Evidence
After: 190 local tests, TypeScript, a zero-vulnerability npm audit, production build, content validation and generated-artifact checks pass. New lint gate reports zero blocking regressions while explicitly retaining 612 pre-existing
anyuses;lint:strictstill exposes that debt.npm run check:project; optional--uiand--securitychecks retain separate receipts. No Lovable agent, model evaluation or generation credits used.Merge Danger
Door: two-way
Apply
20261023120000_mcp_outcome_events.sqlbefore deploying v2 telemetry. It only extends allowed event names and preserves old rows, quotas and RLS. Version evidence may be unavailable and must not be inferred as a pass. Existing type debt and 23 content heuristic warnings remain explicit; this is not a complete security or typing audit.Blast Radius: application
Homepage copy, marketplace trust display, auth return paths, MCP telemetry and delivery checks. Review the formatting commit separately. Live email delivery/OAuth providers and paid checkout were not exercised.