-
Notifications
You must be signed in to change notification settings - Fork 1
feat: recover TEPP validation on canonical Project history (v2.19.0) #339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
seonghobae
merged 37 commits into
feat/project-history-timeline-v2184-r3
from
feat/tepp-project-history-recovery-v2210
Aug 21, 2026
Merged
Changes from all commits
Commits
Show all changes
37 commits
Select commit
Hold shift + click to select a range
f1ff05c
test: specify recovered TEPP project-history boundary
seonghobae 93873f7
test: specify TEPP project-history buyer evidence
seonghobae 565e531
feat: recover strict TEPP project-history client
seonghobae 8281e6a
feat: map canonical project history into TEPP contract
seonghobae 5c81a5e
feat: render TEPP validation beside canonical history
seonghobae 889bddb
style: add TEPP project-history evidence panel
seonghobae 2a2a1a7
docs: add TEPP project-history Storybook states
seonghobae 31c2016
chore: stage one-shot TEPP project-history recovery
seonghobae 0b03ad5
docs: record recovered TEPP project-history boundary
seonghobae 26b83f0
ci: execute verified TEPP project-history recovery
seonghobae 19747b6
fix(i18n): cover Vietnamese TEPP project-history copy
seonghobae 065f962
test(red): require TEPP evidence on canonical timeline
seonghobae 7d2fea8
fix(ci): make TEPP recovery red gate integration-specific
seonghobae 3fd75b0
fix(ui): harden TEPP evidence semantics and accessibility
seonghobae f8b5826
test(ui): cover TEPP evidence labels and unique regions
seonghobae a1b117f
test(red): reject unrecognized TEPP findings and invalid responses
seonghobae 704215a
fix(ci): apply complete strict TEPP recovery contract
seonghobae 32e24c1
ci: format and lint TEPP recovery before commit
seonghobae 8d69a34
docs(adr): close TEPP finding vocabulary and response boundary
seonghobae 69f0a3d
fix(ci): cancel stale TEPP recovery attempts
seonghobae cb30c24
feat: materialize TEPP project history recovery
seonghobae 337691a
test: keep TEPP evidence type-safe
seonghobae 065d582
fix: fail closed on unknown TEPP findings
seonghobae 13a3430
fix(http): let strict contracts suppress LLM metadata
seonghobae 6dfb5d9
fix(tepp): keep contextual metadata out of strict payloads
seonghobae 1703bf7
test(tepp): prove strict payloads suppress LLM metadata
seonghobae 8baf402
fix(tepp): preserve strict validation while suppressing metadata
seonghobae 43262dc
fix(tepp): normalize unexpected provider failures
seonghobae 1df9d83
Merge remote-tracking branch 'refs/remotes/origin/feat/project-histor…
seonghobae 87c1b01
fix: enforce TEPP project history byte limits
seonghobae 6a4dbe7
fix: order TEPP history events by timestamp
seonghobae 76964c0
fix: sanitize TEPP transport provider errors
seonghobae 8d12743
docs: record TEPP provider error boundary
seonghobae 59d687e
Merge latest project history timeline into TEPP recovery
seonghobae b3d803a
feat: connect Ask answers to canonical project histories (v2.20.0) (#…
seonghobae b450c3e
Merge branch 'feat/project-history-timeline-v2184-r3' of https://gith…
seonghobae 9235807
docs: assign unique ADR numbers after stack merge
seonghobae File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| ### Fixed | ||
|
|
||
| - Bind the Global Ask knowledge cutoff in the final authorized-source query. | ||
| - Give the post-chat cutoff migration a unique `0054` identity and remove | ||
| self-modifying stabilization workflows. |
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔍 Analysis-run TEPP submission still forwards LLM metadata
This PR added
include_llm_metadatatopost_jsonprecisely so a closed non-LLM contract cannot leak an unpublishedmetadatamember (http_client.py), and the project-history client opts out via_post. The pre-existing analysis-run TEPP transport inconfigured_tepp_client(analysis_run_start.py) was not updated and still callspost_jsonwith the defaultinclude_llm_metadata=True, so if an LLM context is active during submission it would appendmetadatato TEPP'sAnalysisRunRequestwire payload. The worker delivery path is unlikely to have an active LLM context, so impact is probably nil today, but the closed-contract rationale applies equally here.(Refers to this code)
Was this helpful? React with 👍 or 👎 to provide feedback.