@dwk/webdav: litmus conformance failing (basic 15/16, copymove/props/locks never run)

[davidwkeith]

Summary

@dwk/webdav's litmus conformance run is currently failing per conformance/status.json:

"litmus": {
  "status": "failing",
  "report": "https://github.com/davidwkeith/workers/actions/runs/30052950880",
  "lastRun": "2026-07-23T23:21:37Z"
}

basic is at 15/16 (a 2026-07-24 percent-encoding fix is mentioned in follow-up discussion but
hasn't been re-verified against a fresh litmus run), and litmus halts after the first failing
test group — so copymove, props, and locks have never actually run yet. Both integration
and the node conformance target are still "pending".

This surfaced while designing Anglesite-app's (this repo's downstream consumer) app-side
WebDAV/Solid-Pod composition — see
Anglesite/Anglesite#TBD for that work, which ships the
app-side plumbing now but treats this conformance status as advisory (mirrors the existing
@dwk/webmention precedent of shipping while conformance is still pending), not a blocker.

Ask

• Re-run litmus per conformance/webdav-qa.md against a target with the percent-encoding fix,
  confirm basic goes to 16/16.
• Let litmus continue past basic so copymove/props/locks actually get exercised at least
  once, and fix whatever those turn up.
• Update conformance/status.json to reflect the real result once green (or once the next
  concrete blocker is known).

References

• conformance/status.json (@dwk/webdav entry)
• conformance/webdav-qa.md (the runbook to re-run this)
• docs(webdav,solid-pod): reconcile WebDAV façade status across docs #465 (docs reconciliation that surfaced this status accurately)

[davidwkeith]

Progress via #468 — all four litmus groups were finally exercised (locally, against the composed conformance target under `wrangler dev --local-protocol https`, each group run individually so one failure can't hide the rest):

• basic 16/16 — `mkcol_over_plain`'s real root cause was neon's `ne_mkcol()` appending a trailing slash (the percent-case fix in fix(webdav): normalize percent-encoding case so MKCOL matches an existing PUT #421 was correct but orthogonal).
• copymove 13/13 — unblocked by making collection DELETE recursive per RFC 4918 §9.6.1 (litmus's `begin` relies on it to clear leftovers; the old 409-on-non-empty wedged every group after `basic`).
• locks 41/41 — required the full (bounded) `If:` grammar with real 412 evaluation, plus shared write locks.
• props 22/30 — the remaining 8 failures are all dead-property storage, which `spec/packages/webdav.md` §4 explicitly excludes from v1. This is the next concrete blocker: litmus cannot go fully green until that spec decision is revisited (implement a dead-property store: new DO-SQLite state, PROPPATCH document-order set/remove, dead props carried across COPY/MOVE) or the exclusion is accepted and the gate re-scoped.

`run-suite.mjs` now runs the groups individually in CI too, so the hosted job will report per-group results instead of halting at the first failure.

Hosted re-run (after #468 merges — conformance.dwk.io auto-deploys from main): needs a fresh app password minted with the operator-held `CONFORMANCE_ADMIN_TOKEN`, the `WEBDAV_USERNAME`/`WEBDAV_PASSWORD` repo secrets updated, then dispatch the Conformance workflow with `standard=webdav`, `target_url=https://conformance.dwk.io/dav/\`. I couldn't do this autonomously (the admin token is operator-held and rotating it via `wrangler secret put` wasn't something I was willing to do unprompted). Expected result: basic/copymove/locks green, props failing on dead properties only — `conformance/status.json` stays `failing` until the dead-property call is made.