Skip to content

Allow evidence-bound fallback date approval - #29

Closed
seonghobae wants to merge 1 commit into
feat/cloud-review-decisionsfrom
feat/reviewed-fallback-date-evidence
Closed

Allow evidence-bound fallback date approval#29
seonghobae wants to merge 1 commit into
feat/cloud-review-decisionsfrom
feat/reviewed-fallback-date-evidence

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Summary

  • keep embedded high-confidence production time as the only automatic date gate
  • permit lower-ranked filename/filesystem evidence only with an exact immutable approved review decision
  • require review for embedded dates below high confidence and mirror the backend policy in the UI
  • keep the headless CLI fail-closed and preserve all copy, path, receipt, sync, and no-deletion invariants

Validation

  • npm run check (0 errors, 0 warnings)
  • npm test (5 files, 18 tests passed)
  • git diff --check
  • targeted Rust coverage added; remote CI is the authoritative compile/test because this disk-constrained host previously killed a clean Rust build under memory pressure

Formatting note

  • repository-wide cargo fmt --check reports extensive pre-existing formatting drift outside this four-file change; no unrelated mechanical reformat was applied

Stack

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant