History

ZDDC 59b5550872 refactor: nest lifecycle slots per-party + add virtual top-level aggregators May 2026 reshape. archive/ is now the only physical project-root directory; working/, staging/, reviewing/ move from the project root into each archive/<party>/ folder. Six top-level URLs become virtual aggregators served via the cascade rather than disk: ssr/mdl/rsk tables rollups across parties with a synthesised $party source-party column working/staging/ browse folder-nav listings of parties with reviewing non-empty content in the slot; per-party URLs 302-redirect to archive/<party>/<slot>/ Mkdir at the project root is restricted to `archive` and `_`/`.`- prefixed system names — virtual aggregator names and ad-hoc folders return 409. Plan Review hardcodes the scaffold convention (archive/<party>/ {reviewing,staging}/<tracking>/); the pre-reshape on_plan_review.{reviewing_root,staging_root} cascade keys are dropped. document_controller is now subtree-admin of every archive/<party>/ (not of project-root working/staging/ as before), so per-party lifecycle slots inherit admin authority through the cascade. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-21 07:57:45 -05:00
..
css	fix(browse): trim markdown read-only banner + drop YAML front-matter placeholder	2026-05-18 09:47:21 -05:00
js	refactor: nest lifecycle slots per-party + add virtual top-level aggregators	2026-05-21 07:57:45 -05:00
build.sh	build: simplify to stable + exact-version (drop alpha/beta as public concepts)	2026-05-20 09:17:46 -05:00
README.md	feat(browse): generic directory listing tool — default at folder URLs	2026-05-03 19:56:51 -05:00
template.html	feat(browse): SPA overhaul — context menu, YAML editor, icons, hovercard, deep links, autofilter	2026-05-14 12:12:42 -05:00

README.md

browse — directory listing tool

Generic file browser for any directory. Designed to work with ZDDC archives but useful for any folder. Single-file HTML, no install.

How it's used

Two modes, auto-detected at page load:

Online (zddc-server backed). When this HTML is served by zddc-server at a folder URL — which it is by default for any directory under ZDDC_ROOT that doesn't have an index.html — the JS queries the same URL with Accept: application/json to load the directory's listing and renders it as a sortable, filterable table.
Local (FileSystemAccessAPI). Click "Select Directory" in the header to pick any folder on your computer. Works in Chromium-based browsers (Chrome, Edge, Brave, etc.). No server required; the directory is read directly from disk.

What it does

Lists files and folders with name, size, type (extension), and modified date.
Click a folder to expand inline. Children load lazily on first expand.
Click a column header to sort by that column. Click again to reverse.
Type in the filter to narrow to entries whose name contains the substring.
Click any file to open it in a new tab — for server-backed pages, this routes through zddc-server's normal handler (so an .archive redirect, an apps cascade override, etc. all work as expected).

Design notes

No ZDDC-specific filtering. This tool is intentionally domain-agnostic. The companion archive tool layers ZDDC parsing (project / status / revision filters, tracking-number resolution) on top of the same listing API. Use archive when you want ZDDC semantics; use browse when you just want to see what's in a folder.
Default at directory URLs. zddc-server's directory.go serves the embedded browse.html bytes for any directory request with Accept: text/html and no index.html present. This means a user navigating to any folder under ZDDC_ROOT gets a usable browser without anyone having to drop a file into the archive.
Apps cascade override. Like every other ZDDC tool, the served browse.html can be overridden per-folder via a .zddc apps: entry. The default is the embedded copy from the binary; operators can pin a specific version or URL if they want.