Upgrade skill: SKILL.md configures two source lanes from user-sources.json, which the payload never ships — both lanes are silently dark on a fresh install #2181

Summary

skills/Upgrade/SKILL.md names user-sources.json as the configuration for two of the skill's source lanes. No example, schema, or template for that file ships anywhere in the payload, so both lanes are dark on a fresh install with nothing to indicate why.

Checked against main at 5e2f2e8c, LIFEOS/VERSION 7.40.4.

Detail

skills/Upgrade/SKILL.md:

line 68 — | GitHub trending | Config: github_trendingblock in useruser-sources.json. ... |
line 69 — | Custom sources | user-sources.json in CUSTOMIZATIONS — fetch each; skip dead/redirected pages with a note |

git ls-tree -r --name-only main | grep -c user-sources
# 0

Nothing in the tree carries that name: no sample, no .example, no schema, and no scaffold step that writes one.

Why it is worth a line

The two lanes fail differently from a broken reference. They simply produce nothing. A user running the skill gets a report that silently omits GitHub trending and every custom source, with no error to explain the gap and no file to look at, because the file that would configure them does not exist and is never mentioned outside those two table cells.

Suggested fix

Ship a documented example — user-sources.example.json alongside the skill, or a block in the skill's own documentation showing the github_trending shape and the custom-source shape. Either is enough to make the lanes discoverable.

If those lanes are meant to be opt-in and empty by default, saying so in the table cell would do the same job for nothing.

Related

Same class as #1187: documentation referencing a file the payload does not ship. Distinct from #1953, which covered UpgradeFanout.js in the same skill's workflow file.