[znerol2]

What & why

An outside reader clicking through the dmfdeploy repositories sees each README first. This change makes that first screen accurate and consistent with the other repositories.

• The README opens with a short header: what the repository is, that it's part of the dmfdeploy open prototype, its status, and a link to the umbrella.
• The read-first install comes before the piped one.
• The supported Debian version matches dmf-infra.
• The README says what the AI agent instruction files at the root are for.
• CONTRIBUTING.md drops a note about a private archive mirror that doesn't apply to outside contributors.

Refs dmfdeploy/dmfdeploy#711

How it's tested

• Every relative link in the changed Markdown files resolves in the tree.
• The changed README has no error-level voice alerts.
• A grep of the added lines finds no local paths, private hostnames or people's names.

[lkirc]

Request changes: the target-node guidance contradicts the dmf-infra documentation it cites.

• README.md:176-180 says dmf-infra documents Debian 13 plus a 4 vCPU / 16 GB / 60 GB minimum. Its current README documents Debian 12 and 3 nodes with 4+ CPU, 8+ GB RAM, and 80+ GB disk; related dmf-infra#101 likewise says Debian 12 is the documented target. Please correct this attribution and the requirements.

[znerol2]

Fixed in 0299c64: the target-node section now describes the running v0.1 sandbox node directly (Debian 13, 4 vCPU ARM64, 16 GB RAM, 60 GB disk, about 7 GB RAM and 30 GB disk used at idle) and no longer attributes those figures to the dmf-infra README. dmfdeploy/dmf-infra#101 states the same facts.

Also in this push: 43ceddc removes a doubled word, and a4d9cc3 pins the one link to the umbrella session notes to a fixed commit, because dmfdeploy/dmfdeploy#713 removes that folder from the tree.

[lkirc]

Approved current head a4d9cc3. The earlier target-node concern is resolved: README.md now identifies the v0.1 sandbox profile as its own and separately states dmf-infra's Debian 12 baseline.