Leave a project you can return to.
Good project notes are short and actionable. Start with the purpose of the project, the command that opens the development environment, and the very next piece of work.
Attach the repository URL and the local directory path. Keep these references current when you move the checkout or rename the repository. Avoid putting secrets into the notes.
At the end of a session, write what changed and what remains unresolved. A clear next step is often more useful than a long activity log.