Add release guidance to integration guide and remove private repo references

- Add 'Releasing Your Engine' section to docs/integration-guide.md explaining
  that engines are consumed via GitHub Releases, with a sample workflow and
  guidance on what to include in the release tarball
- Remove all references to the private github/agent-platform-engine-example
  repo from both README.md and docs/integration-guide.md

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: GitHub Copilot

README.md

@@ -14,8 +14,6 @@ The Copilot Engine SDK provides everything you need to build an engine that runs
 - **CLI** — local testing harness that simulates the platform for development
 - **[Integration Guide](docs/integration-guide.md)** — step-by-step guide to building an engine
 
-> **📦 Reference Implementation** — See [`github/agent-platform-engine-example`](https://github.com/github/agent-platform-engine-example) for a complete working engine built with this SDK.
-
 ## Installation
 
 Until this package is published to a package registry, install it directly from GitHub:
@@ -242,7 +240,6 @@ Engines receive these environment variables from the platform:
 ## Documentation
 
 - **[Integration Guide](docs/integration-guide.md)** — step-by-step guide to building an engine from scratch
-- **[Example Engine](https://github.com/github/agent-platform-engine-example)** — reference implementation
 
 ## Contributing
 

docs/integration-guide.md

@@ -6,8 +6,6 @@
 
 This guide walks you through building a custom **engine** — a program that receives a coding task from the Copilot platform, runs an agentic loop against a repository, and streams progress back to users in real time.
 
-> **📦 Reference Implementation** — See [`github/agent-platform-engine-example`](https://github.com/github/agent-platform-engine-example) for a complete working engine built with this SDK.
-
 ## What Is an Engine?
 
 An engine is a program that the platform executes when a user triggers a coding task — such as assigning Copilot to an issue, requesting changes on a PR, or invoking a task via the API. The platform creates a **job**, launches your engine in a secure runner environment, and your engine does the work.
@@ -896,6 +894,67 @@ async function main() {
 }
 ```
 
+## Releasing Your Engine
+
+Engines are consumed via **GitHub Releases** rather than by cloning and building the source repository. Each release should contain a self-contained tarball with everything the platform needs to run your engine: the `engine.yaml` definition and your compiled build output.
+
+### Creating a Release
+
+Tag your commit and push the tag — a GitHub Actions workflow builds the project and publishes the release automatically:
+
+```bash
+git tag v1.0.0
+git push origin v1.0.0
+```
+
+### Release Workflow
+
+Add a workflow that triggers on version tags, builds your engine, and attaches the artifact to a GitHub Release:
+
+```yaml
+# .github/workflows/release.yml
+name: Release
+
+on:
+  push:
+    tags:
+      - 'v*'
+
+permissions:
+  contents: write
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+
+      - run: npm ci
+
+      - run: npm run build
+
+      - name: Create release tarball
+        run: tar -czf engine.tar.gz engine.yaml dist/
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v2
+        with:
+          files: engine.tar.gz
+          generate_release_notes: true
+```
+
+### What to Include in the Release
+
+Your release artifact must include `engine.yaml` and everything it references. The `entrypoint` in `engine.yaml` is resolved as a relative path, so any files or directories it points to need to be in the tarball alongside it. For example, if your entrypoint is `node dist/index.js`, then `dist/index.js` (and any of its runtime dependencies) must be present.
+
+The release should be self-contained — the platform should be able to extract it and run the entrypoint without cloning the repo, installing dependencies, or building from source.
+
+
 ## Architecture Notes
 
 ### Tokens