pdf-metadata-viewer-cloud

IN BUILD

The tool works but only exists on one machine, pointed at one folder, which means the household archive is only tendable from that desk. Moving it to the hub's existing Vercel pipeline makes it reachable, and doing that for one user first defers multi-tenancy, subprocessor agreements, and Google's restricted-scope security assessment until there's evidence the hosted workflow is even pleasant to use.

STAGES

  1. proposal08-14
  2. requirements08-14 ↻ 08-18
  3. design08-14 ↻ 08-18
  4. tasks08-14
  5. build—
  6. archived—

CAPABILITIES — 3 IN ONE CHANGE

  • document-metadata-store6 requirements
  • drive-document-source7 requirements
  • hosted-instance-access5 requirements

OUTCOMES — 34 OF 67 DONE, AND NOT MAPPABLE TO A CAPABILITY

This change organises its tasks by workstream rather than as spec scenarios, so progress cannot be split per capability.

WHERE THE SOURCES DISAGREE

2.1b — the change says 2.1b still expects work on #389; the record shows #389 merged on 2026-08-18.

  • a commit for #389 is on this branch, dated 2026-08-18

WHAT HAPPENED

  1. TASKS

    proposal and specs and design and tasks landed

    2026-08-14 · 1 pull request
    • #371feat(pdf-metadata-viewer): hosted single-tenant instance on labs

  2. 4 days quiet — nothing touched this change

  3. ↺ BACK TO SPECS + DESIGN

    feat(pdf-metadata-viewer): full Drive scope for folder import

    2026-08-18 · 1 pull request
    • #389feat(pdf-metadata-viewer): full Drive scope for folder import

History read from a manifest built at 2026-09-30 (09e7bcc).

2 pull requests, found by commits touching the change folder