summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJesse Vincent <jesse@fsck.com>2026-10-07 19:27:14 -0700
committerJesse Vincent <jesse@fsck.com>2026-10-07 19:27:14 -0700
commite4dc1ced68b7eef84f61f040502fdfb03db8fc50 (patch)
tree97ca33eb053c155f6d3e32dd141a1b7efaee20cd /docs
parenteabbe888edf50ebb39d5bf7e02eb1aa860a864b1 (diff)
docs(porting): Appendix A shows examples, not every harnesscodex-sync-excludes-and-porting-examples
It called itself the live index of reference integrations, which it can't stay without an update for every new harness, and it had already fallen behind (no Devin, Hermes, or Muse). Present it as worked examples of each integration shape and point to the repo's manifests as the source of truth.
Diffstat (limited to 'docs')
-rw-r--r--docs/porting-to-a-new-harness.md11
1 files changed, 7 insertions, 4 deletions
diff --git a/docs/porting-to-a-new-harness.md b/docs/porting-to-a-new-harness.md
index ce37418..37d6893 100644
--- a/docs/porting-to-a-new-harness.md
+++ b/docs/porting-to-a-new-harness.md
@@ -8,8 +8,8 @@ It is written in two layers. **Part 1–3** explain how the system works and how
to tell whether a harness can be supported at all; read these before you touch
anything. **Part 4–8** are a prescriptive procedure for an agent (supervised by
a human partner) to execute the port end to end, through distribution. An
-appendix indexes the current reference integrations so you can copy the closest
-one.
+appendix gives worked examples of each integration shape so you can copy the
+closest one.
The integration mechanism differs across harnesses, and it will keep changing.
This guide deliberately teaches the **invariants** — the things that must be
@@ -790,9 +790,12 @@ dispatcher pattern.
---
-## Appendix A — Reference integrations (current)
+## Appendix A — Reference integrations (examples)
-Use this as the live index; when in doubt, read the files, not this table.
+One or more worked examples of each integration shape, to copy from. This is
+not a list of supported harnesses, and it isn't updated for each new one — the
+manifests in the repo are the source of truth. When in doubt, read the files,
+not this table.
| Harness | Entry point | Bootstrap mechanism | Tool mapping | Tests | Distribution |
|---|---|---|---|---|---|