Skip to content

docs: Conduit ecosystem packaging and agent guide - #5

Draft
jordanpartridge wants to merge 4 commits into
mainfrom
cursor/conduit-ecosystem-docs-6412
Draft

jordanpartridge wants to merge 4 commits into
mainfrom
cursor/conduit-ecosystem-docs-6412

Conversation

@jordanpartridge

@jordanpartridge jordanpartridge commented Sep 10, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Rebased onto latest main. Docs-only positioning of cf in the Conduit ecosystem (docs/conduit.md, AGENTS.md, README section, demo walkthrough).

Test plan

  • CI green
  • Skim README + docs/conduit.md on GitHub
Open in Web Open in Cursor 

@lexi-chief-of-staff lexi-chief-of-staff Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking items:

  • README links to docs/agent-output.md which does not exist.
  • docs/conduit.md reference claims richer agent recipes than what the new file actually contains.

Other notes:

  • CI workflow, AGENTS.md, composer metadata, and ecosystem positioning are clean.
  • composer.lock bump is large but expected from the PHP 8.3 + updated deps.

No runtime changes; docs/packaging only. Ship after the two doc links are fixed.

@jordanpartridge
jordanpartridge force-pushed the cursor/conduit-ecosystem-docs-6412 branch from 170c0e2 to 638d263 Compare September 10, 2026 05:51

@lexi-chief-of-staff lexi-chief-of-staff Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking: composer.json is invalid after the edit.

  • composer.json:60 adds "scripts" directly after "bin" array without a trailing comma on the preceding line, producing parse error.
  • No other issues; docs and README changes are clean and match the stated intent.

@jordanpartridge

Copy link
Copy Markdown
Contributor Author

Addressed the blocking review:

  • composer.json on this HEAD parses (JSON_OK); the scripts block already has a trailing comma after bin.
  • README no longer links to docs/agent-output.md (that file is not on this branch). --json is documented as pretty-printed API output.
  • docs/conduit.md now includes the tunnel:expose recipe and command-map row.

Please re-review 5361a53.

@lexi-chief-of-staff lexi-chief-of-staff Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ship it.

  • Docs-only + packaging; no runtime changes.
  • composer.json scripts and keywords are additive and match the new agent focus.
  • AGENTS.md and docs/conduit.md give clear, actionable guidance for both humans and agents.
  • Single docblock addition in CloudflareConnector is harmless.

@jordanpartridge
jordanpartridge force-pushed the cursor/conduit-ecosystem-docs-6412 branch from 5361a53 to ace2458 Compare September 10, 2026 13:37

@lexi-chief-of-staff lexi-chief-of-staff Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ship it.

  • One factual mismatch: composer.json change claims a lockfile update that isn't present.
  • Docs and agent guidance are self-consistent and match the stated intent.
  • New test covers the expected doc invariants.
  • No runtime or correctness changes; packaging/docs only.

All other files look clean. Ready after the lockfile note is addressed.

jordanpartridge added a commit that referenced this pull request Sep 10, 2026
PR #5 must not claim docs/agent-output.md or the {ok,data} envelope
(that is unmerged #7). Fold demo.md / demo.cast.md from #4; leave
the hero README crew and PHAR install alone.

@lexi-chief-of-staff lexi-chief-of-staff Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ship it.

  • AGENTS.md, docs/conduit.md, demo files, and README ecosystem section match the locked spec exactly (honest --json shape, tunnel:expose coverage, no agent-output.md references).
  • composer.json keywords/description and platform.php 8.3.33 preserved; tests/Unit/ConduitDocsTest.php enforces the invariants.
  • No runtime changes, no envelope claims, no sibling-command conflicts.
  • Ready for merge.

cursoragent and others added 4 commits September 13, 2026 00:42
Add agent-facing Conduit docs and AGENTS guide, link sibling tools
from the README, enrich Packagist keywords, and add a Pest CI workflow.

Co-authored-by: Jordan Partridge <jordan@partridge.rocks>
Add AGENTS.md, conduit recipes, hero README, and a demo walkthrough.
Enrich Packagist keywords. Document tunnel:expose. Do not link a
missing agent-output spec. Leave PHAR install to a later PR.

Co-authored-by: Jordan Partridge <jordan@partridge.rocks>
PR #5 must not claim docs/agent-output.md or the {ok,data} envelope
(that is unmerged #7). Fold demo.md / demo.cast.md from #4; leave
the hero README crew and PHAR install alone.
Keep main README install and development. Document pretty-printed
API result, tunnel:expose JSON keys, and jq paths. Demo files from
the hero-readme branch, patched for tunnel:expose.
@cursor
cursor Bot force-pushed the cursor/conduit-ecosystem-docs-6412 branch from d371a08 to b479950 Compare September 13, 2026 00:46

@lexi-chief-of-staff lexi-chief-of-staff Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking: README still documents the envelope behavior that this PR (and spec.md) explicitly rejects.

  • Line 69 (and downstream sections) still say {"ok":true,"data":...} and link to missing docs/agent-output.md.
  • Commands, Expose, and tunnel:create paragraphs repeat the stale description.
  • docs/conduit.md, AGENTS.md, and the new test all assert the correct raw-result shape; README was only half-patched.

Fix the remaining prose or drop the conflicting sections before merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants