docs(tizen): record the rc2 device evidence and executed CI - #2
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 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.
Documentation only. Brings two stale claims back in line with what has actually happened, and records the first CI-built signed install.
BUILD.md
Its Evidence and limits block had fallen behind
ACCEPTANCE.md. It still said the corrected production-identity package was not installed and that playback acceptance was open, whileACCEPTANCE.mdhas recorded confirmed playback under the real identity for some time. It also said CI had never run and no release was published; there are now several green runs and three releases.The early "installed but closed immediately" history is kept, but marked as superseded rather than reading as current state.
ACCEPTANCE.md
No GitHub workflow execution is claimed.and records the actual run: https://github.com/balcsida/plezy/actions/runs/35648745086, tagtizen-v2.20.1-rc2, both jobs green.a76d6153…, source-input SHA-2565f2d2403…, revision16b0ae89, clean tree, hash re-checked inside the deploy container immediately before install. In-place signed upgrade, no uninstall, no data cleared.Run the checked-in GitHub workflow and record its actual run URL.item.What is deliberately not claimed
Independent cryptographic verification and Samsung entitlement stay open, and the device-matrix rows are untouched.
inspection.jsonstill reportscryptographic_signature_verified: falseandtv_installation_verified: false; the text now says explicitly that a later successful install does not retroactively change a build-time structural report.Retail
sdbdrefuses arbitrary shell verbs, so process liveness was never confirmed from the CLI — onlyapplistandwas_executeare available. That limitation is stated rather than glossed over.AI assistance
Written with Claude Opus 5 via Claude Code, per CONTRIBUTING.md.
🤖 Generated with Claude Code