A project archive becomes more useful when its history is understandable without reconstructing it from scattered commits.
The Lab records chronology through project lifecycle history and dated timeline entries. That is enough to answer an important question: what engineering state was documented at each point in the project’s life?
The boundary matters. These records are historical documentation, not live telemetry. A project can change in its source repository without the Lab claiming that every runtime state is known.
As the archive grows, durable dates and explicit transitions are more valuable than a synthetic activity feed.