ForgeFlow 0.10.7

Reliable server-to-repository recognition

Live, running workloads with one unique exact provenance or runtime-identity match are now linked automatically during normal server discovery.
Automatic adoption creates only ForgeFlow configuration and observed state; it performs no container changes and never automatically removes stale profiles.
Ambiguous, duplicate, external and monitoring-only workloads remain behind explicit Review & link confirmation.
Every linked repository now displays an S deployment badge with its profile count in the repository sidebar.
The repository release rail reports Linked with container and server identity even when a legacy workload has no verifiable live commit yet.
DevRunbook-style DockerMan deployments therefore show the same linked relationship in Deployments, the repository sidebar and the repository workspace.