chore: integrate device-trust continuation into main #79
No reviewers
Labels
No labels
auth
bug
composer
correctness
database
durability
enhancement
feeds
interactions
notifications
performance
reliability
safety
security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
starsetbyte/peregrine!79
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/device-trust-foundation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Integration cleanup
Promotes the completed
feat/device-trust-foundationcontinuation intomain.Included merged continuation work:
The feature branch has been independently verified through the host gates on the code PRs; the final merge should leave
maincontaining the density/P1 handoff, all P2 continuation work, and accurate project documentation.Integrated directly into
mainas merge commitf97b143after Forgejo’s PR merge endpoint rejected the stale pending status bridge and does not allow its advertisedmanually-mergedstyle. The exact merge commit passed:app:testDebugUnitTest,:app:lintDebug, and:app:assembleDebug. Closing this integration PR as already integrated.Content from
feat/device-trust-foundationshipped tomainvia a local--no-ffmerge, which is why Forgejo shows this closed-unmerged rather than merged. Reconciled indocs/reviews/2026-07-25-branch-pr-reconciliation.md, which landed onmainvia #103. Branch deleted as part of that reconciliation.Pull request closed