chore(gitea): regenerate the flat content mirror after the ADR-0020 retrofit
Generated output, not authored content: scripts/sync-plugin-content.sh --all. Claude Code has no .apm/ awareness, so this compiled mirror must track .apm/ or the check-plugin-content-sync pre-push hook reports drift. Deferred to a single commit at the end of the wave on purpose. sync_dir runs rm -rf before every copy, so running it while seven agents were editing the same plugin would have raced them; agents were told not to sync for that reason. Refs #99
This commit is contained in:
@@ -57,7 +57,11 @@ scope applied at once.
|
||||
1. Read the conversation context (issue/PR title, body, or the triggering discussion) for the
|
||||
signals above.
|
||||
2. Call `label_read method: "list_repo_labels"` (see `references/labels.md`) to get the current
|
||||
label set with IDs — inference must never guess an ID, only a name, then resolve it.
|
||||
label set with IDs — inference must never guess an ID, only a name, then resolve it. Because
|
||||
`exclusive` is an org-labels-only flag, this taxonomy plausibly lives at org scope too: for any
|
||||
inferred name absent from the repo pool, also call `label_read method: "list_org_labels"` with
|
||||
`org` set to the repo's `owner` before treating it as unresolved. A failure there means the owner
|
||||
is a user account, not an organisation, so no org pool exists and the name is genuinely absent.
|
||||
3. Match inferred label names against the resolved list (case-insensitive). If a scope group
|
||||
already has a different label applied on the target and a new one is inferred for that same
|
||||
scope, plan to replace rather than add (see above).
|
||||
|
||||
Reference in New Issue
Block a user