Tasks Backlog and tracking for tiny-pattern-ts. Managed in vscode-todotasks format. --- Setup: ☐ Add gitea release page in CI @high ☐ Split off template into separate package => pi --session 01a07dde-7050-7054-bb36-1606d7eb2bc3 @high v1.0: ☐ API surface is stable and fully typed ☐ Finalize public exports in `src/index.ts` ☐ Document all exported types and functions ☐ Add JSDoc for public APIs ☐ Test coverage meets threshold ☐ Achieve 100% branch coverage on `src/pattern.ts` ☐ Achieve 100% branch coverage on `src/match.ts` ☐ Achieve 100% branch coverage on `src/index.ts` Bugs: Enhancements: Documentation: ☐ Add usage examples to README.md ☐ Create `examples/` directory with runnable snippets ☐ Add comparison section vs. other TS pattern-matching libs ☐ Write migration guide for users coming from discriminated unions ☐ Create backlog tasks for implementation Maintenance: ☐ Serve CI coverage over a tiny self-hosted webserver (replace the zip artifact) @low ☐ Add a minimal dir-listing webserver to the gitea docker setup (e.g. caddy `file_server browse` reusing the existing reverse proxy, or any single-binary static server, lipanski/docker-static-website) ☐ CI writes each run's `coverage/` into a shared volume keyed by project + tag (e.g. `/coverage/tiny-pattern-ts//`) ☐ Browse to `…/coverage///index.html` in the browser; drop the `actions/upload-artifact` coverage step in favour of the shared-dir layout → design: no deploy step in CI; the webserver just exposes the shared directory (decided over Gitea Pages / Codecov — neither confirmed available/ wanted) ☐ serve docs over self hosted server @low ☐ Add a minimal dir-listing webserver to the gitea docker setup for serving docs (reuse existing reverse proxy) ☐ CI writes docs to a shared volume keyed by project + tag (e.g. `/docs/tiny-pattern-ts//`) ☐ Browse to `…/docs///index.html` in the browser ☐ serve landing page over self hosted server @low ☐ Add a minimal dir-listing webserver to the gitea docker setup for serving landing page (reuse existing reverse proxy) ☐ CI writes landing page to a shared volume keyed by project + tag (e.g. `/landing/tiny-pattern-ts//`) ☐ Browse to `…/tiny-pattern-ts/index.html` in the browser