ci: add a type: chore label, and record the uvx MCP launch

[JoottunAtish]

What this changes

Two related repository-configuration changes, both now declared. Closes #14.

1. Adds type: chore to the label taxonomy.
2. Records the .mcp.json launch change that was already on this branch.

Type

• Build, CI, or tooling

1. The label

The taxonomy had no label for test-only or tooling work, so #13 ("add the missing tests to paths.go") had nowhere correct to sit. type: refactor means "internal change with no behaviour change", and adding a missing test is not that.

Meanwhile the branch naming rule already used chore as one of its three kinds, so the word was in the vocabulary with no label behind it.

2. The MCP launch change

This was undeclared in the first version of this PR. The review caught it, and this is the fix.

.mcp.json launches both servers through uvx rather than by calling the installed binary directly. That is intentional and it stays: the direct-binary form did not connect reliably, and the uvx form does.

Rather than reverting it, the reasoning is now recorded in the code-navigation skill where the next person will actually look, along with the two consequences that are easy to miss:

• uvx resolves the package at launch, so the version that runs is whatever it picks rather than whatever is installed.
• --watcher is no longer passed to jcodemunch, so there is no filesystem watcher. Reindexing relies on the PostToolUse hooks, which fire on Edit and Write. If the index looks stale, call register_edit rather than waiting for a watcher that is not running.

That skill section also gained the operational knowledge this session cost us to learn: editing .mcp.json mid-session connects nothing until the window is reloaded, and indexing docs here needs include_dot_dirs: [".claude"] or the skills holding the project's rules are silently absent from the index.

Also in here

• PROGRESS.md quoted "32 labels" in two places, which adding a label made wrong. Both now point at .github/labels.yml as the source of truth instead of repeating a number. Second time that line has drifted, so removing the count beats incrementing it.
• .gitignore now covers __pycache__ and *.pyc. Writing this commit staged two bytecode files from the pytest suite, because Python only arrived in this repository with the CI gate checker and nothing ignored its caches.

Checklist

• ./scripts/check-punctuation.sh passes
• ./scripts/check-links.sh passes
• ./scripts/sync-labels.sh applied cleanly, 0 failed
• Label applied to [ticket] platform: test paths.go, closing a real coverage gap #13 to confirm it sticks
• Verified no .pyc or __pycache__ path is tracked
• Not applicable: no Go code, so gofmt, vet, tests and the layer test are unaffected
• Not applicable: no new dependency, no user-facing error, no subprocess call

Platforms exercised

• Windows, locally

Notes for the reviewer

sync-labels.sh never deletes labels absent from the file, deliberately, because deleting one silently removes it from every issue that carried it. So the label change is additive only.

Separately, the review noted that five GitHub default labels (bug, documentation, enhancement, invalid, question) shadow the type: taxonomy and undermine the one-type:-label rule. Not fixed here, since it is a deletion rather than an addition and deserves its own change. Tracked as a follow-up.

[JoottunAtish]

Review of my own PR, so this is a comment rather than an approval: GitHub does not allow self-approval, which is the exact situation the RepositoryAdmin bypass in the ruleset exists for.

One blocking issue, one should-fix, one suggestion. All eight checks are green and I verified the label sync independently, so the label change itself is sound. The problem is what came along with it.

---

blocking: this PR contains an undeclared, unrelated change

The diff is two files, not one. .mcp.json has been rewritten from direct binary invocation to uvx:

-      "command": "jcodemunch-mcp",
-      "args": ["serve", "--transport", "stdio", "--watcher"],
+      "command": "uvx",
+      "args": ["jcodemunch-mcp"]

The title says "add a type: chore label", the description talks only about labels, and the linked ticket #14 is scoped to labels.yml. A reviewer approving on the description would not know the MCP configuration changed.

This violates the one-logical-change rule in the github-workflow skill, and it matters more than tidiness here: the two changes have different blast radii. The label addition is additive and reversible. The MCP change alters how this repository's tooling launches for every contributor, and it cannot be reverted by removing a label.

On its merits the uvx form is defensible and probably correct, because the direct-binary form did not reliably connect while the uvx form did. But two things in it are behavioural changes nobody declared:

• --watcher is dropped from jcodemunch. That flag enabled filesystem watching and auto-reindexing. The code-navigation skill claims hooks handle reindexing on Edit and Write, so this is probably fine, but it is a capability removal and it should be a stated decision rather than a side effect.
• uvx resolves the package at launch, so the version that runs is whatever uvx picks, not the version installed on the machine. That is a supply chain posture change in a repository that just spent a whole ticket pinning GitHub Actions to commit SHAs for exactly that reason.

Requested fix: split it. Either drop .mcp.json from this branch and file it as its own chore ticket, or keep it and rewrite the title, description and ticket to cover both, explicitly noting the --watcher removal and the uvx resolution behaviour. The first is cleaner.

should fix: this PR makes PROGRESS.md wrong in two places

PROGRESS.md on main states the label count twice:

line 33:  | Label taxonomy | 32 labels defined in `.github/labels.yml`, ... |
line 92:  - 32 issue labels defined in `.github/labels.yml` and applied by

The PR head has 33. I verified by counting ^- name: on the branch.

Small, but it is the kind of drift that makes a progress document stop being trusted, and the implementation skill's Definition of Done asks for PROGRESS.md to be updated when a change alters what exists. Either correct both numbers or replace them with something that cannot go stale, for example "the label taxonomy is defined in .github/labels.yml" with no count.

suggestion: five GitHub default labels shadow the taxonomy

Not caused by this PR, but directly adjacent to it and worth catching while we are here. Comparing the declared set against the live repository:

on GitHub but NOT in labels.yml:  bug  documentation  enhancement  invalid  question

Those are GitHub's repository defaults. bug, documentation and enhancement duplicate type: bug, type: docs and type: feature, and they actively undermine the "exactly one type: label per issue" rule, because sooner or later somebody applies bare bug and the taxonomy quietly stops meaning anything.

sync-labels.sh deliberately never deletes, which is the right default, so these will linger until removed by hand. Worth a follow-up ticket to delete the five and note in the script's header that the repository defaults were pruned once on purpose.

What I verified rather than assumed

• 33 labels on the PR head, up from 32
• d4c5f9 appears exactly once, so no colour collision. The repeated colours in the file (1d76db, 5319e7, b60205) are the intentional area:, platform: and severity families, not accidents.
• ./scripts/sync-labels.sh applied cleanly: 33 created, 0 failed, and the awk parser handled the new entry
• Every declared label exists on GitHub, so the sync is complete
• type: chore applied to #13 and it stuck
• All eight checks green, including the branch-name gate on chore/issue-14

Safety review: not applicable to the label change. The .mcp.json change touches local tooling launch only and cannot reach a learner's machine, but see the uvx version-resolution note above.

[JoottunAtish]

All three review findings addressed in d3fa116.

blocking, the undeclared .mcp.json change. Resolved by declaring it rather than reverting it, since the change is correct and intentional: the direct-binary form did not connect reliably and uvx does. The title, description and ticket #14 now cover both changes, and the code-navigation skill records the reasoning plus the two consequences that were the real risk of leaving it silent, namely that uvx resolves the package version at launch and that --watcher is no longer passed so reindexing depends on the hooks.

should fix, the stale label count. Both occurrences in PROGRESS.md now point at .github/labels.yml instead of quoting a number. It had already drifted twice, so removing the count is better than incrementing it.

suggestion, the shadow labels. Filed as #17, with the zero-usage check already done for all five so the deletion is provably safe.

One thing the review did not catch, found while committing: nothing ignored __pycache__, because Python only entered this repository with the CI gate checker. Writing the commit staged two .pyc files. .gitignore now covers them and I verified no bytecode path is tracked.

Diff is now five files: the label, the MCP config, the skill, PROGRESS.md, and .gitignore.