weichen f628e6b38b Advance DHF Documents pin after main sync ...

Why: The Documents main gained an unrelated merge-queue report before PR submission, so the feature branch must include the current authoritative base.

Evidence: Comparing c256558 and fdca353 shows only the merge-queue report changed; the DHF plan, index and asset inventory retain their bytes. Dev combination tests follow on this exact pin.

Impact: Update the Documents gitlink and stage-seven trace; no DHF package, publication or runtime data change.

Refs: .task/feature-dhf-template-pipeline-plan.md

2026-10-14 06:37:41 +00:00

..

backend @ 8e80e2618e

Pin the merged account transaction backend

2026-10-14 04:15:55 +00:00

core @ 5773e74086

Compose system project membership implementation candidates

2026-10-13 09:57:00 +00:00

documents @ fdca353097

Advance DHF Documents pin after main sync

2026-10-14 06:37:41 +00:00

frontend @ 5313cfad4e

Pin delivered frontend export and record current dependency

2026-10-14 03:19:40 +00:00

ui @ 2c4322ef56

Bump UI and frontend pins to picker integration

2026-10-13 09:36:36 +00:00