chore(ci): point the chain check and the devcontainer pointers at .docs/

The move left the chain check reading a directory that no longer exists: dev
check and the traceability job in build.yml called it with --spec-root docs
and would have stopped with exit 2. Both now pass --spec-root .docs, still
explicitly rather than through the script's default, and the comments next
to the two calls name .docs/specs/.

Neither workflow filters on the layer path, and pom.xml names no includes or
excludes: the source and javadoc jars are built from the source roots under
src/, so
the layer never reached an artifact under either name.

The pointers to the devcontainer research note in ~/.claude — in dev, in
devcontainer.json and twice in the pre-push hook — follow its new path as
well; that layer has already moved.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: glaudeee

.devcontainer/devcontainer.json

@@ -1,7 +1,7 @@
 {
   // Devcontainer-Sicherheitsmodell: Push aus Container ist hart geblockt (DEVCONTAINER=true + pre-push-Hook).
   // Keine Credentials im Image, kein SSH-Agent-Forwarding, keine Cred-Mounts.
-  // Quelle: ~/.claude/docs/project/research/devcontainer-architektur.md
+  // Quelle: ~/.claude/.docs/project/research/devcontainer-architektur.md
   "name": "java-predicates",
 
   // 2026-05-13: JDK 25 LTS zum Zeitpunkt dieser Vorlage. Verfuegbarkeit pruefen mit:

.githooks/pre-push

@@ -2,7 +2,7 @@
 # Devcontainer Push-Block-Hook.
 # Verhindert git push aus dem Devcontainer.
 # Host (WSL/Mac) pusht unblockiert -- DEVCONTAINER-Env nur im Container gesetzt.
-# Quelle: ~/.claude/docs/project/research/devcontainer-architektur.md
+# Quelle: ~/.claude/.docs/project/research/devcontainer-architektur.md
 
 if [ "${DEVCONTAINER:-}" = "true" ]; then
   echo "" >&2
@@ -11,7 +11,7 @@ if [ "${DEVCONTAINER:-}" = "true" ]; then
   echo "[pre-push] Devcontainer hat keine Credentials und darf keine haben." >&2
   echo "[pre-push] Push vom Host (WSL-Distro / Mac), dort liegen die Token." >&2
   echo "[pre-push]" >&2
-  echo "[pre-push] Konzept: ~/.claude/docs/project/research/devcontainer-architektur.md" >&2
+  echo "[pre-push] Konzept: ~/.claude/.docs/project/research/devcontainer-architektur.md" >&2
   echo "" >&2
   exit 1
 fi

.github/workflows/build.yml

@@ -34,7 +34,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      # Neither Maven nor a JDK: the check only reads docs/specs/ and the
+      # Neither Maven nor a JDK: the check only reads .docs/specs/ and the
       # *Test.java files as text. It rides in its own job rather than inside
       # the `build` matrix because it has nothing to do with which JDK
       # compiled the code -- in the matrix it would run three times over and
@@ -44,5 +44,5 @@ jobs:
       # filenames don't match the default *Test.java scan.
       - name: Check requirement <-> test chain
         run: |
-          python3 bin/traceability/traceability.py --spec-root docs --source-root . \
+          python3 bin/traceability/traceability.py --spec-root .docs --source-root . \
             --source src/test/java/com/github/zrdj/java/predicates/testcases

dev

@@ -6,7 +6,7 @@
 # den Befehl direkt aus. Damit ist `./dev <cmd>` ueberall derselbe Aufruf und es
 # gibt keinen Weg, versehentlich nativ zu bauen.
 #
-# Hintergrund: ~/.claude/docs/project/research/devcontainer-architektur.md
+# Hintergrund: ~/.claude/.docs/project/research/devcontainer-architektur.md
 set -euo pipefail
 cd "$(dirname "${BASH_SOURCE[0]}")"
 
@@ -58,7 +58,7 @@ check)
 	echo -e "${GREEN}Full check (tests)...${NC}"
 	mvn -B -ntp test
 	# Prueft, dass jeder [impl->req~...] in *Test.java auf eine Anforderung
-	# unter docs/specs/ aufloest (Kette kaputt -> Exit 1) und dass die Pruefung
+	# unter .docs/specs/ aufloest (Kette kaputt -> Exit 1) und dass die Pruefung
 	# selbst ueberhaupt gelaufen ist (Aufruf-/Selbstpruefungsfehler -> Exit 2,
 	# der gefaehrlichere Fall: ein Zweier hier hiesse "Pruefung lief nicht",
 	# nicht "Kette sauber"). `set -e` reicht beide Exit-Codes unveraendert nach
@@ -71,7 +71,7 @@ check)
 	# explicitly. Without it, every [impl->req~...] added there would be
 	# invisible to this check despite compiling and running correctly.
 	echo -e "${GREEN}Checking requirement <-> test chain...${NC}"
-	python3 bin/traceability/traceability.py --spec-root docs --source-root . \
+	python3 bin/traceability/traceability.py --spec-root .docs --source-root . \
 		--source src/test/java/com/github/zrdj/java/predicates/testcases
 	;;
 *) usage ;;