chore(backlog): sync issues and pull requests#521
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d6d983f7eb
ℹ️ 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".
| <li><a href="https://github.com/octokit/rest.js/commit/5f380d04bbb71a9c2d3d241438378e6ebffe2597"><code>5f380d0</code></a> build(deps-dev): Bump form-data from 4.0.2 to 4.0.4 in /docs (<a href="https://redirect.github.com/octokit/rest.js/issues/520">[[520-feat-skills-add-create-goal-skill-for-well-formed-session]]</a>)</li> | ||
| <li><a href="https://github.com/octokit/rest.js/commit/dc6827d06231ae01ba85608b64d0c7e4b9bd6e04"><code>dc6827d</code></a> build(deps-dev): Bump tar-fs from 2.1.2 to 2.1.3 in /docs (<a href="https://redirect.github.com/octokit/rest.js/issues/516">[[516-feat-add-check-registry-and-migrate-frontmatter-markdown]]</a>)</li> |
There was a problem hiding this comment.
Preserve upstream issue numbers in mirrored Dependabot notes
Keep the original upstream issue references here instead of replacing them with local wikilinks: these two commit bullets now display [[520-...]]/[[516-...]] even though the link targets are octokit/rest.js issues. When local backlog IDs collide with upstream issue numbers, this rewrite corrupts the mirrored changelog text and creates misleading local cross-references for readers and any tooling that consumes wikilinks.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ed6ed4d406
ℹ️ 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".
|
|
||
| This generalises to issue resolution (one-shot, bounded), daily brief (recurring, awareness), incident triage (rapid tempo), release readiness (checklist gate), and continuous awareness (perpetual). Software examples are illustrative; the method does not assume a software-engineering context. | ||
|
|
||
| The full method, vocabulary, state model, and quality gates are locked in [`plugin-v2/docs/method.md`](../tree/claude/unified-plugin-v2-Lmn8x/plugin-v2/docs/method.md). |
There was a problem hiding this comment.
Replace broken relative tree link with absolute GitHub URL
This mirrored backlog entry rewrites the method reference to ../tree/claude/..., which resolves relative to docs/backlog/ and points to a non-existent docs/tree/... path, so readers cannot open the referenced document from the canonical backlog file. For synced PR bodies, this should remain an absolute GitHub URL (or another resolvable path) to preserve navigable traceability.
Useful? React with 👍 / 👎.
Summary
docs/backlog/Verification
npm run sync:backlognpm run check:backlogNotes
This PR is generated by
.github/workflows/sync-backlog.yml.