added validation section to moongate file download() function, and associated tests

converted all 'edit' requests from POST to GET

removed quotes fromn route-names, tidied up route definitions

modified DPW download() to match equivalent Moongate method so it also can handle absolute or relative docs_path

modified Moongate download() to work with relative docs_path - previously returned 'not found' message

moved documents_path setting to config_local.yml files to allow site-specific configuration; Moongate documents_path now defined in config_local.yml (same way DPW docs_path is defined); new test file for household based on moongate.t, most dpw.t tests now skipped as they are not htmx-aware

added test error to save_document() methods; create_document() flash message adjusted for update or input; refactored infolib.t to inspect redirected content [see HTTP-Cookies.txt chatgpt summary]; bugfix to dpw/record.tt

converted dpw section to SPA using htmx; renamed moongate new-document route to match other route prefixes; removed unused route names; removed unused all_documents() subs from all route files; new test file for htmx requests

converted moongate section to SPA using htmx

applied same change to Moongate model as in previous commit

moved file save function from Moongate route to model, equivalent to recent DPW modification

extended app to provide household/dpw function; provided session expiry time display; increased dev env cookie_duration (but session still times out too early); sync'd InfoLib & Moongate save_document() methods with DPW class (using global @cols)

search function returns to home page instead of summary if no records found

major rewrite - combined separate docs-lib and moongate apps into single app using prefixes with multiple route files; merged DB functions into model which is now a D2 plugin, providing encapsulated model domains (infolib, moongate & dpw); uses route names to allow tt to call uri_for_route, but some caveats: * route names must be unique across all route files * uri_for_route cannot be used in any template loaded after a forward since the data required in request.uri_for_route($name) is deleted during the forwarding process leading to fatal error when tt calls the uri_for_route function; META function no longer works since tt WRAPPER function disabled to allow routes to define layout