STATECONSOLE
Keep client work and side projects moving.
When you’re the only developer across a client repository and your own product, you decide what moves next. StateConsole brings reported project status and open tasks from your local workspace into one view.
Two repositories, one decision
Fictional example. Both repositories are registered as Active. You have time to finish one piece of work before the end of the day.
- Studio Booking · client project
- A time-zone bug is Ready for review. The client expects an update today, and you have the local fixtures needed to check the fix.
- Field Notes · side project
- The next action is to configure an import. A representative input file is still missing, so you leave the import blocked.
You choose Studio Booking because you can complete the review today and give the client an update backed by evidence. The guide to managing multiple coding projects covers the routine for checking blockers and deciding where to resume.
From project status to a tested fix
- Set Studio Booking as your Focus Project. With the bug as its open task, Continue Working shows the time-zone fix as the next task to review.
- Review the diff in your usual coding tools. Move the bug to Testing and check bookings at 23:55 and 00:05 in the studio’s local time zone.
- Record the results in the task. A Bug or QA task needs a recorded Passed result in Testing before it can move to Done. StateConsole records the result you enter. You run the checks and judge the evidence.
- Expected
- The 23:55 and 00:05 bookings show their respective local calendar dates.
- Actual on the local test build
- Both bookings showed the expected date. Result recorded as Passed.
Use the QA checklist to record test scope and results. The Developer Task Manager shows how those records fit into the task workflow.
Leave the next session a clear starting point
Update Studio Booking’s PROJECT_STATUS.md with the two checks you ran and the next step of sending the client an update. Task edits do not rewrite the repository report. Use the status-file template and setup guide to keep that report in the supported format.
For Field Notes, leave a short note to get a representative input file and then test the import with it. The AI coding session handoff guide has a template for carrying that context into your next session.
See how the Dashboard brings it together
Purchasing and downloads are not available on this site yet.