mirror of
https://github.com/morluto/rea.git
synced 2026-11-18 20:53:00 +00:00
* fix(evidence): derive default authority from subject binding evidenceEnvelopeForAdmission defaulted a missing authority to shipped-artifact for every observation, including ones with no artifact subject and ones produced by a live debugger session. An unbound record therefore claimed authority over an artifact it cannot name, and live GDB, Rizin and Cutter observations could never qualify a live-observation contract because that contract accepts only controlled-replay or external-service Evidence. Default to analyst-inference when no subject is bound and keep shipped-artifact when one is, so the default matches what the record can actually support. Declare controlled-replay at the eight live debugger observation sites (GDB 6, Rizin 1, Cutter 1) so those records describe the controlled replay they performed and satisfy the documented contract. * fix(gdb): label retained process-exit observations as controlled replay The GDB command process-exit branch was the only unbound retention path that named no authority, so this branch's new default derived it as analyst-inference. That label cannot support the live-observation contract, and every sibling path (timeout, cancellation, protocol failure, startup) already states controlled-replay. The authority and the unavailable-subject reason now live beside the provider identity so the retention paths read them from one place instead of repeating the literals and drifting apart. * style(evidence): apply repository formatting * fix(cutter): classify command observations as external-service The bridge drives the documented already-running Cutter GUI, whose document state REA neither owns nor resets, so its command observations claim no controlled replay. Label them external-service like the comparable IDA and Frida bridge evidence: live-observation obligations still accept it, while controlled-replay-only verifier contracts and bundle replay scenarios no longer include these observations. * fix(adb): keep device observations at external-service authority The admission default now derives authority from the subject, so a subjectless ADB observation fell to analyst-inference. A device is a service REA attaches to rather than drives, so the observation supports external-service and must stay eligible for live-observation contracts. Carry an explicit authority through AnalysisObservation so a producer that knows its own authority can name it, and set it for every ADB operation. * fix(adb): keep retained observations at external-service authority The admission default derives authority from the subject, and a subjectless observation falls to analyst-inference. createAnalysisExecution never carried an authority field, so every observation the ADB adapter built through it was committed at the subject-derived default instead of the service's. Name the authority once in the domain model, stamp it on every successful execution at the adapter boundary, and route the cleanup-failure and cancellation-retention sites through one helper. Open the execution options field so other providers can name their own authority. Verified: a push whose device digest does not match now retains its receipt at external-service; removing the stamp fails that assertion. check:fast passes. * fix(adb): keep the retained verification receipt at device authority The verificationFailed branch built its retained receipt with createEvidence directly, so the admission default derived the authority from a subjectless target and labelled an observed push as analyst-inference. Pass the device authority through the same way the neighbouring digest-mismatch partial does, so the receipt can still support live-observation verification. * style(adb): apply oxfmt formatting to the authority fix The previous commit wrapped two expressions that oxfmt keeps on one line, so npm run format:check failed on Static checks.