Repository navigation
docs: record public release evidence - #4
Conversation
Signed-off-by: Josh Gier <129348785+Josh-Gi3r@users.noreply.github.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cb65f819b7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| `d36f3933`. They were later published through reviewed PR #1; the resolver shell correction | ||
| was published through reviewed PR #2: |
There was a problem hiding this comment.
The reviewed commit message has no Signed-off-by trailer, so any PR containing this commit will fail the repository's required DCO Check. Recreate the commit with git commit -s before publishing it.
AGENTS.md reference: AGENTS.md:L112-L112
Useful? React with 👍 / 👎.
| | Every crate denies all unsafe Rust | Unsupported | Platform-specific unsafe allowances exist. | | ||
| | The fork automatically installs upstream desktop releases | Unsupported | Branch automation detects stable release tags and prepares a reviewed PR; it never auto-merges. | | ||
| | Upstream release detection is currently live | Unverified | Its contract passed at local candidate `4e2e785d`, but the workflow still needs publication and an enabled successful default-branch run. | | ||
| | Upstream release detection is currently live | Verified for detection/conflict path | Default-branch run 31493736853 detected `desktop-v0.5.9`, aborted conflicts safely, and opened issue #3. Clean integration-PR creation remains unobserved. | |
There was a problem hiding this comment.
After this row classifies the detector as live for the detection/conflict path, the linked docs/development/fork-and-upgrades.md still calls it a “local candidate” and states that it has not been pushed, merged, or proven live. Readers following the evidence trail therefore receive mutually exclusive status information; update that guide to record the published workflow and observed conflict run as part of this evidence refresh.
Useful? React with 👍 / 👎.
Summary
mainand the livedesktop-v0.5.9conflict-reporting pathValidation
node scripts/audit-public-docs.mjs— 76 Markdown files, 143 local linksscripts/test-upstream-desktop-sync-contract.shgit diff --checkThis is an evidence-only follow-up to PRs #1 and #2.