# Todofile This is a "to do next" file, particularly useful to keep the human and a coding assistant in sync. The format is based on [Keep a Todofile V0.0.1](https://coulomb.social/open/KeepaTodofile). The structure organizes **future tasks** by their impact, just as a changelog organizes past changes by their impact. *** ## [Unreleased] - *Active Vibe-Coding State* 💡 This section is for tasks currently being discussed with or worked on by the coding assistant. These are the ephemeral, flow-of-thought tasks. ### NPM Publication - Remaining Tasks **Status**: Phases 1-6 complete ✅ (build system, bundling, testing) **Remaining**: Phases 7-9 (pre-publication, publication, post-publication) #### Phase 7: Pre-Publication Setup - [ ] Run `npm pack` to create package tarball - [ ] Test packed version locally (`npm install ./testdrive-jsui-1.0.0.tgz`) - [ ] Setup npm account (`npm login` or create account) - [ ] Decide repository structure (separate repo vs monorepo) - [ ] Create git tag: `git tag -a v1.0.0 -m "Release v1.0.0"` - [ ] Run final pre-publish checks: - `npm run lint` (no errors) - `npm test` (all tests pass) - `npm run build:prod` (clean build) - `npm publish --dry-run` (verify what will be published) #### Phase 8: Publication - [ ] Publish to npm: `npm publish` - [ ] Verify package on npmjs.com - [ ] Wait 5-10 minutes, then verify CDN availability: - jsdelivr: `https://cdn.jsdelivr.net/npm/testdrive-jsui@1.0.0/dist/testdrive-jsui.min.js` - unpkg: `https://unpkg.com/testdrive-jsui@1.0.0/dist/testdrive-jsui.min.js` - [ ] Create GitHub release from v1.0.0 tag - [ ] Test fresh install: `npm install testdrive-jsui marked` #### Phase 9: Post-Publication - [ ] Add npm badges to README.md - [ ] Create live demo page (optional) - [ ] Setup GitHub Pages for demo (optional) - [ ] Create announcements (optional) - [ ] Monitor downloads and feedback ### Other Tasks - [ ] Make sure that Markitect integration still works fine - [ ] Update STANDALONE_PLAN.md and decide if it should be implemented *** ## Completed Tasks *Recent completed tasks have been documented in CHANGELOG.md following Keep a Changelog format.*