Status

Not a primary task. First, we need to achieve a simple and reliable single-project lifecycle infrastructure. Portfolio management makes sense to develop on top of working primitives, rather than designing them for the sake of future centralization.

Why the task should still be recorded

As the number of serviced websites grows, a distinct problem arises: mass updates, status checks, and exception searches must not require sequential manual traversal of each project.

In the future, a layer may be needed that is aware of available projects and their infrastructure capabilities, allowing an agent to address operations to multiple projects. However, the specific form of such a control plane is not yet defined and should not dictate the architecture of the core system.

Principle

First:

reliable Project lifecycle -> clear runtime/deploy/restore primitives

And only then, once real operations reveal recurring needs:

multiple Projects -> common orchestration/control layer

Related to the main task of lifecycle infrastructure and accelerated launch of new websites.