Repository navigation
Foreman 1.2.3
Added
- New employee opens on Pick a job: choose one of Foreman's fifteen jobs and Add makes that employee approved and ready at once; Write your own keeps the Generate way. (#204)
- The program manager asks you her questions before she plans, all on one card: answer each, or tell her to Plan with what you have. For a large project she assumes nothing she could ask. (#205)
- A project's plan is drawn as a workflow, with what the program manager understood, when it is done, what is out of scope and any assumptions to check, and
plan.mdcarries the same, with the questions and your answers. (#205) - A project's Parts card can show the parts as a map (List | Map): what runs at the same time, what waits for what, and where each part is; selecting a part takes the channel to its newest post. (#208)
- The Team page shows Hand-offs outside projects: each chain of work one employee handed to another, drawn as a map with the actions waiting for you on it. (#208)
- A project's channel shows who is at work on it now, on what and for how long, with Watch to open their chat, or Nothing running when no one is. Its row in the sidebar and on the Channels page shows a turning ring while someone works. (#209)
- The sidebar's groups, such as Needs your attention and Agents working, now fold under cards like Channels, remembered across launches; a folded Needs your attention still shows how many need you. (#203)
Changed
- Employees picked from a job template follow a prompt written for their job: how it is done, what they hand back, when they ask, and they no longer claim tests passed when nothing ran. (#210)
- A project started in a channel keeps its workspace in the channel. It no longer appears under the sidebar's or Home's workspaces unless it needs you. (#207)
- Once a plan is in effect, its table shows each part's State. (#208)
Fixed
- An organization's project no longer stops with "Maximum of 10 chats per workspace" after about ten employee runs; a workspace can now keep up to 100 chats open. (#206)
Development
- A
project-partsscreen in the screenshot fixture. (#208)
Known validation findings
npm run check:security did not finish its scan of Git history: Gitleaks stopped at its 5-minute limit after scanning about 4.3 GB across all refs, with no leaks found in what it scanned. The source and lockfile scans found no secrets.
Full changelog: v1.2.2...v1.2.3