hemantkumar822/flowkit
v0.3.0-preview.1MIT
Proportional engineering with durable project state and verification evidence.
Changelog
0.3.0-preview.1 — 2026-10-27
- Curated, self-contained product brief/story/architecture and review procedures adapted from audited MIT-licensed upstream sources.
- Full upstream copyright/license notices, pinned Git-blob source hashes, derivative hashes and modification records in the installed skill and release archives.
- Read-only CLI template discovery; no framework installation or execution required.
- Product roadmap separates this curated foundation from future artifact gates, schema migrations, team recovery and host certification.
0.2.1 — 2026-10-27
- Preserve literal whitespace and empty arguments in verification commands; reject NUL input. Regression observed failing before correction.
- Readable source formatting and consistent repository line-ending rules; no added runtime dependency.
- Explicit project-document and project-memory policy, including the distinction between agent-authored documents and CLI scaffolding.
- Clean source and release inventories; publication remains a separate action.
- Refuse silently replacing a versioned release archive with different contents; preflight all output paths before writing.
0.2.0 — 2026-10-27
- Portable core with explicit Codex, Claude Code and Cursor installation paths, user/project scope and custom-path fallback. Non-Codex host workflows remain unverified.
- Optional integration discovery and original baseline methods when external skills are absent.
- MIT license for original code, third-party notices, native compatibility manifests and synchronized version metadata.
- Allowlisted deterministic ZIP/npm archives, checksums and real packed-artifact installation tests; developer/private evidence excluded from distributions.
- Reusable product README, user guides, security/contribution policies and maintenance roadmap.
0.1.0 — 2026-10-25
- Initial Codex coordinator skill and zero-dependency Node CLI.
- Local onboarding, task transitions, evidence freshness, status and lessons.
- Explicit GitHub issue/PR drafts and guarded apply operations.
- Owned installation, update backups and reversible removal.
- Environment/source research and isolated behavioral evaluations; see evaluation for limits.