persp-projectile VS consult-project

I am currently trying with perspective rather than persp-mode, as it segregates the buffer list as I like (#1 above). I've got projectile with persp-projectile, and that seems to give me what I need for project navigation (#2 probably, still not 100%). I get some help in my mode line for project focus (#3, partially).

Aye. I often have two interdependent projects I work on simultaneously, and I use a lot of persp-projectile (https://github.com/bbatsov/persp-projectile). I would love to try project.el but sadly it seems like it doesn't integrate with perspective.el yet.

I also use purely emacs for "commercial programming" (as you refer to it) and for managing multiple projects I use projectile + perspective + persp-projectile.

I had my own rolled version of this in my config until recently when I swapped to perspective and perspective-projectile.

Consult-project defines an endpoint for accessing different sources related to the common project workflow. Using Consult's narrowing system, the user is able to access the current project's buffers, project files and all the known projects, in case they want to change projects quickly. Consult-project provides an extension to the default Consult functionality, using the built-in package project.el, defining the functions consult-project and consult-project-other-window. Furthermore, Consult-project only depends on consult, resulting in a lean and simple to maintain functionality.