Repository navigation
Docs: clarify Pattern Sample Locks qualification evidence - #1242
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.
Follow-up to the owner review on PR #1235.
This evidence-only update corrects
tests.summaryto bind the reported MKII trial to a unit reporting configuration SHA9680e9ac…, and says no physical MAIN hash/readback was recorded. It records the unexplained high-load SAMPLE-field changes with cause unknown, redacts personal cache paths throughout the module evidence, and adds a TESTING cross-reference to the stock-free production package/USB report.The package report records the actual public-wrapper build/check and private USB fixture: candidate checkout
91d8d493aecea91ae9f4cc9857393e3e06535743, tested upstream base3ae8c38d1b1bba48e3ca4368f83dffd5ff70b724, native-source fingerprint7ea0fbdf317bfdab6a82b22869c7029ba23901cd27a3337a4bdaf8f8beeb7e69, and byte-identical package (10,048 bytes) SHA-2563e13c46fb0054d05f228b045746453e0c50dbbe52fb53b3c229d598ddd7fed79. It lists the pinned Octabam/Elekloader inputs, host compiler and assembler hashes, builder/recipe hashes, commands, both stock scans, five expected refusal probes, seven public-base add/removal Undo preflights, and all 30 Octatrack package preflights. The first attempt pointed--upstreamat Octabam and stopped at the Elekloader import; the corrected input was the pinned Elekloader checkout. This was an input-path correction, not a source or package mismatch. Private receipt hashes and paths are recorded in the report; no firmware, extracts, card data, or raw dumps are in Git.The branch follows upstream through
d5e5f7122ebcd39ebd9ce6d43ce4d9a914d9e924. PR #1215 added a separate Rytm package/catalog row; PR #1085 added Rytm plain/send-bus bases and a shared Elekloader selector registered only for Rytm. PR #1232 added an Octatrack emulator parent-exit watchdog and refreshed infrastructure/source-build proof records, includingstandalone-recipes.jsonandmodule-build.json. These updates did not change the Pattern Sample Locks native source, public package wrapper, host reconstruction builder, candidate reconstruction recipe, or pinned Elekloader kit/tool source. The report remains bound to91d8d493/3ae8c38d; no build or emulator result is claimed at current based5e5f712. The current separate Elekloader catalog checks at revisione249c55(10 cores, 58 mods, 69 assets); Rytm entries are outside the 30-package Octatrack fixture.Validation: Node 24
npm run pr:ready -- --remote upstreamreturned Ready at based5e5f712; 343 JavaScript files passed (2,814 passed, 2 skipped), SDK checks passed (515 run, 20 skipped), and host upload checks passed (39). Guide correction: nothing; these are candidate-specific evidence corrections.This does not promote the draft or change runtime, version, or catalogue. Hardware qualification remains incomplete: no physical MAIN readback, complete stack/memory or worst-case cycle bound, full stress/persistence result, or first-release owner review is established; the owner release-path answers on PR #1088 remain pending.