WORKFLOW.md D1.6 ends "Required for every C# and Python repo that has tests (see spec/secrets.json typeMechanisms)". WORKFLOW.md is carried whole into every fleet repo, and a downstream spec/secrets.json is a repo-scoped adaptation per docs/repo-config-carry.md, which carries typeMechanisms only where a real mechanism routes to it. In every other repo the pointer names a key its own copy of that file does not contain.
ESPHome-Config is one: its spec/secrets.json carries baseline alone, which the carry doc prescribes for a source-only repo whose publish targets all map to a null mechanism. Copilot raised it there as a low-confidence finding on ptr727/ESPHome-Config#93, and I declined it locally on the grounds that a carried file may not be edited to say "see the hub" and that the reword, if it is worth making, is worth making fleet-wide.
Nothing is broken by it. D1.6 is N/A in a repo with no tests, and whole-file carry deliberately keeps guarantees a repo does not exercise. It is a pointer that reads as actionable and is not, in most of the copies it ships to.
The reword would have to survive both readings, since the same sentence ships to a repo where the key is present and to one where it is not. Something naming the fleet spec as the definition, rather than the reader's own copy of the file.
WORKFLOW.mdD1.6 ends "Required for every C# and Python repo that has tests (seespec/secrets.jsontypeMechanisms)".WORKFLOW.mdis carried whole into every fleet repo, and a downstreamspec/secrets.jsonis a repo-scoped adaptation perdocs/repo-config-carry.md, which carriestypeMechanismsonly where a real mechanism routes to it. In every other repo the pointer names a key its own copy of that file does not contain.ESPHome-Configis one: itsspec/secrets.jsoncarriesbaselinealone, which the carry doc prescribes for a source-only repo whose publish targets all map to a null mechanism. Copilot raised it there as a low-confidence finding on ptr727/ESPHome-Config#93, and I declined it locally on the grounds that a carried file may not be edited to say "see the hub" and that the reword, if it is worth making, is worth making fleet-wide.Nothing is broken by it. D1.6 is N/A in a repo with no tests, and whole-file carry deliberately keeps guarantees a repo does not exercise. It is a pointer that reads as actionable and is not, in most of the copies it ships to.
The reword would have to survive both readings, since the same sentence ships to a repo where the key is present and to one where it is not. Something naming the fleet spec as the definition, rather than the reader's own copy of the file.