Fix CI: untrack docs prose, correct two stale frontend specs

wilm has been red for eight consecutive runs across backend, gates and
frontend. Three failures, two unrelated causes, neither introduced by the
endpoint agent work.

docs/ prose (backend + gates):
The docs gates detect a published checkout by the ABSENCE of docs/*.md,
because docs/ becomes the wiki on that side. DEV-BUILD-TEST.md and
PLUGIN-HOOKS.md were committed in unrelated changes, which made CI look
like an internal checkout carrying almost no prose. test_there_are_docs_
to_check then failed on `assert 3 > 20`, test_the_map_itself_is_current
failed on a generated PROJECT-MAP.md that is correctly untracked, and
check-gates-ran.sh failed on the resulting skip - a skipped gate reports
green and checks nothing, so it refuses to accept one.

The existing .gitignore comment predicted this exactly and was defeated by
naming files individually. Untracked both (kept on disk) and replaced the
per-file list with docs/*.md so the next authored doc cannot reintroduce
it. Scoped to the top level: docs/notes/ prose and docs/openapi.json stay
tracked, and the gates only glob docs/*.md.

Frontend specs:
getEntraDeviceUrls() gained lapsUrl and loaded, but two siteSettings specs
still asserted the old two-key shape with toEqual, which is exact-match.
The implementation is correct - loaded is what lets a caller distinguish a
failed fetch from an unconfigured site, since both read as empty strings -
so the specs were brought up to the current shape rather than the return
value narrowed.

pinnedPanels.spec.js sliced 420 characters from getEntraDeviceUrls() and
asserted the finally block appeared inside it. Adding the retry logic
pushed finally past that offset, so a correct implementation reported as
"the finally is missing". Rebounded the slice to the function's own extent,
matching the structural approach already used elsewhere in this file for
the same reason. Verified by mutation: renaming the flag in the source
fails the test, which also caught that the spec reads
plugins/computers/frontend/views/PCDetail.vue and not the .plugins-staged
build copy.

.gitignore

@@ -91,20 +91,24 @@ _transfer/
 # Local developer scratch notes and chat handoffs - never committed
 devnotes/
 
-# docs/ is generated/published to the wiki, not tracked in the product repo.
-# A single tracked file here makes docs/ exist in the CI checkout, which
-# defeats the intentional skip in the docs publish/version tests. Keep this
-# local-only guide out of version control so those tests skip as designed.
-docs/CSV-IMPORT-GUIDE.md
+# docs/ prose is published to the wiki, not tracked in the product repo. The
+# docs gates detect a published checkout by the ABSENCE of docs/*.md, so a
+# single tracked prose file here makes CI look like an internal checkout while
+# carrying almost no prose: test_there_are_docs_to_check then fails asserting
+# >20 files, test_the_map_itself_is_current fails on a generated PROJECT-MAP
+# that is correctly untracked, and check-gates-ran.sh fails on the resulting
+# skip. That happened - DEV-BUILD-TEST.md and PLUGIN-HOOKS.md were committed in
+# unrelated changes and broke the branch for days. Ignore the whole pattern
+# rather than naming files one at a time, so the next authored doc cannot
+# reintroduce it.
+#
+# Scoped to the top level on purpose: docs/notes/ prose stays tracked, and the
+# gates only glob docs/*.md. docs/openapi.json is tracked (the app serves it)
+# and is unaffected by a *.md rule.
+docs/*.md
 
-# Local-only authored docs (executive summaries, workflow/security writeups,
-# planner exports, draft decks and diagrams). Same reasoning as above: keep
-# personal docs out of version control. docs/openapi.json stays tracked and
-# is intentionally NOT ignored here.
-docs/EXECUTIVE-SUMMARY.md
-docs/DESIGN-DECISIONS-agent.md
-docs/OPERATOR-WORKFLOW.md
-docs/SECURITY-RISK-ASSESSMENT.md
+# Local-only authored docs (planner exports, draft decks and diagrams). Same
+# reasoning as above: keep personal docs out of version control.
 docs/ShopDB-Planner-Tasks.csv
 docs/DRAFT--ShopDB-CSV-Import-Guide.pptx
 docs/diagrams/