Tag v0.1.0 + Packagist publication (HITL)

[fbarrento]

What to build

Cut the v0.1.0 release and publish to Packagist once #2 through #9 are in main.

This issue is HITL because Packagist submission requires the maintainer's account credentials and a one-time form submission.

Source design: see project_sdk_design.md in the project's memory.

Acceptance criteria

• CHANGELOG.md filled in under ## [0.1.0] - <release-date> listing each MVP resource and the foundation work
• README install section uses composer require phpdevkits/forge-sdk:^0.1
• README has a clear callout: "Tracks Forge API v0.x; minor versions may break until 1.0"
• Annotated git tag v0.1.0 pushed to origin
• GitHub release created from the tag, with notes summarizing the MVP scope and linking to the design memory
• Repo submitted to Packagist at https://packagist.org/packages/submit (one-time)
• GitHub → Packagist webhook configured for auto-update on push
• Smoke test: in a fresh directory, composer require phpdevkits/forge-sdk resolves to 0.1.0; Forge::fromEnvironment()->me() succeeds against a real Forge token (run by the maintainer, not in CI)

Blocked by

• Blocked by Tracer bullet: $forge->me() end-to-end + credential factories #2, Organizations resource + Page<T> + list-options pattern #3, Providers catalog (read-only) #4, Hybrid org context + Servers CRUD #5, SSH Keys (under server) #6, Sites (under server) CRUD #7, Deployments (under site) #8, Daemons / Background Processes (under server) #9