teamcopilot 0.4.14

teamcopilot 0.4.14\n\nThis release adds session-scoped workflow allowlisting so a chat session can opt into always allowing a workflow during that session. The permission prompt and tool-call UI were updated to reflect the new behavior, and the backend now tracks and enforces the session allowlist state.\n\n## Highlights\n- Added a new workflow session allowlist flow for 'always allow in this session'.\n- Updated chat permission handling and tool-call display to surface the new session state.\n- Added schema and migration support for storing the allowlist data.\n- Added backend and route regression tests covering the new workflow session behavior.\n\n## Notes\n- This release is focused on workflow permission ergonomics and does not introduce a broader API shape change.\n- Published from the same commit that passed the release dry run and build checks.

0.4.13

What's changed\n- Added English schedule summaries to cron cards so structured cron expressions are easier to read in the UI.\n- Fixed the table scrolling issue in the chat view.\n\n## Verification\n- npm release helper dry run passed\n- npm publish completed successfully

0.4.12

Changes

• Increased the backend JSON body limit to 10 MB so large file edits can be saved without hitting Express's default 100 KB request cap.
• This fixes the 'request entity too large' failure when saving big files from the UI.

Release checks

• Published to npm as teamcopilot@0.4.12.
• The release helper's test suite and build completed successfully before publish.

0.4.11

Fixes\n\n- Fixed cronjob execution-step serialization so multiline steps, leading dashes, and blank lines are preserved correctly.\n- Switched cronjob prompt storage to a versioned encoded payload for new saves.\n- Kept backward compatibility for existing cronjobs saved with the legacy "Todo steps to follow:" format.\n- Added tests covering the new round-trip behavior and legacy fallback parsing.\n

teamcopilot 0.4.10

What's changed\n- Fixed the cronjob create/edit form on mobile so the panels and inline controls stack cleanly instead of overflowing.\n- Made the schedule builder and raw cron expression views stay in sync when editing an existing cronjob.\n- Rehydrated builder fields from existing cron expressions for the common daily, weekly, and monthly schedules supported by the UI.\n\n## Verification\n- npm release dry run passed\n- npm publish succeeded for teamcopilot@0.4.10

0.4.9

What's Changed\n- Prevent the runWorkflow plugin from starting a second workflow when the latest session message already contains an active workflow tool call.\n- Add tests covering the allowed single-workflow path and the rejected concurrent-workflow path.\n- Update the upgrade checklist to verify the latest-message lookup and concurrency guard behavior.\n\n## Verification\n- npm test\n- npm run build\n- npm publish (via release helper)

0.4.6

Changes\n- Reduced chat message pagination so long conversations open faster and load older history in smaller chunks.\n- Optimized session polling with a recent-session index, which cuts down the work needed to refresh the sidebar.\n- Made usage syncing incremental and fixed the case where an in-progress assistant turn could be synced too early with zero cost.\n- Added regression coverage for first-sync, incremental-sync, and incomplete-assistant usage scenarios.\n\n## Notes\n- This release focuses on chat/session performance and correctness for usage tracking.\n- The npm package was published from the same commit as this tag.

0.4.5

TeamCopilot 0.4.5 fixes the cronjob edit flow in browsers that do not expose crypto.randomUUID().

Fixes

• The cronjob edit/create form now generates execution-step IDs with a browser-safe fallback instead of assuming crypto.randomUUID() is always available.
• This prevents the production error seen when opening an existing cronjob for editing.

Notes

• No server-side behavior changed in this release.
• The change is limited to the frontend cronjob form.

0.4.4

TeamCopilot 0.4.4 fixes the cronjob edit flow in browsers that do not expose crypto.randomUUID().

Fixes

• The cronjob edit/create form now generates execution-step IDs with a browser-safe fallback instead of assuming crypto.randomUUID() is always available.
• This prevents the production error seen when opening an existing cronjob for editing.

Notes

• No server-side behavior changed in this release.
• The change is limited to the frontend cronjob form.

0.4.3

TeamCopilot 0.4.3 focuses on cronjob todo handling and the editing experience.

Cronjob todo handling

• Optional todo steps are now parsed out of the saved cronjob prompt instead of being sent to OpenCode as part of the runtime prompt.
• When a prompt cronjob run starts, those saved steps are pre-seeded into the run todo list before the agent sees the task.
• The first agent instruction now tells the agent to inspect the task and existing todos, then add more todos if needed.

Cronjob editor improvements

• The create/edit cronjob form now supports reordering execution steps with a simple move-down control.
• The form blocks saving if a user types the legacy todo marker into the prompt textarea directly and asks them to use execution steps instead.
• The cronjob list and edit screen both use the shared prompt parser so saved steps still appear correctly when reopening an existing cronjob.
• The old final prompt preview was removed because todo steps are no longer included in the prompt that gets sent to the agent.

Reliability and tests

• Shared prompt parsing/building logic now lives in a dependency-free backend utility used by the backend, frontend, and tests.
• Added coverage for prompt parsing, prompt reconstruction, cronjob dispatch seeding, and route behavior.