chore: re-sync oss-owned files via scaffold --apply

.claude/jit-context/paths/01-oss/changelog-fragments.md

@@ -17,8 +17,10 @@ read out of context.
 
 **A `removed` fragment must declare compatibility**, as one more bullet in that list:
 
-    - Compatibility: breaking - <reason>
-    - Compatibility: compatible - <reason>
+```
+- Compatibility: breaking - <reason>
+- Compatibility: compatible - <reason>
+```
 
 `/oss:release` reads it to propose the version. A removal that declares nothing stops the proposal
 and names the file, rather than being read as a quiet minor -- whether a removal breaks anything is

.claude/jit-context/tools/01-oss/merge-gate.md

@@ -30,8 +30,9 @@ rename, an external-contributor PR, or anything irreversible.
   the default branch is the backstop that tests the real combined content regardless of whether
   the base moved underneath it (`skills/manager/phases/merge.md`, #1085). Only something other
   than staleness -- a real, stated reason -- justifies rebasing before merging.
-- **Do not route around a denied merge.** Say the call was denied, name it exactly, and let
-  the maintainer run or permit it.
+- **A denied merge follows SKILL.md's classifier-denial rule (#1724): retry the identical call
+  once, report the outcome either way, never a second time, never reworded.** Say the call was
+  denied, name it exactly, and let the maintainer run or permit it.
 
 Full argument, the `|force` opt-outs and their blast radii, the rerun-vs-moved-base trap, and
 the branch-deletion rules: `skills/manager/phases/merge.md`.

.claude/jit-context/vocabulary/01-oss/00-index.tsv

@@ -1,9 +1,9 @@
 dev	dev-lanes.md	
 devs	dev-lanes.md	
-developer	dev-lanes.md	generic
-developers	dev-lanes.md	generic
-lane	dev-lanes.md	generic
-lanes	dev-lanes.md	generic
+developer	dev-lanes.md	
+developers	dev-lanes.md	
+lane	dev-lanes.md	
+lanes	dev-lanes.md	
 oss	oss-loop.md	
 the loop	oss-loop.md	
 maintainer loop	oss-loop.md	

.oss/README.md

@@ -14,6 +14,17 @@ why this directory exists at all:
 
 To change something here, copy it out and point your own config at the copy.
 
+## Found a bug in one of these files?
+
+A defect in a file under `.oss/`, or in `.github/workflows/oss-changelog.yml` (the one
+exception below), is not this repository's bug. It ships from https://github.com/Digital-Process-Tools/claude-oss, and this
+directory is replaced wholesale on every `/oss:scaffold` run, so a patch or a test written
+against it here is undone at the next resync — silently, with no error, whenever that
+resync happens. Report it there instead, with a reproduction, the same way you would report a
+bug in any dependency you did not write. Never patch or test the file in this repository, and
+never let a scan, a triage sweep or a fix lane close a finding here as this repository's own
+issue — file it upstream and stop.
+
 ## The one exception
 
 `.github/workflows/oss-changelog.yml` is ours too and is replaced the same way. It