Repository navigation
Add 25-related-services: two repositories, linked PRs, human merge order - #7
Conversation
A factory that spans two related repositories sharing one contract: a Go API (acme/api-service, provider of openapi.yaml) and a Node web app (acme/webapp, consumer). The foreman decides which repository changes first (the provider, additively), the implementer opens one pull request per repository with per-repository bootstrap, tests, and a contract check (including the consumer's check against the provider's current main), a reviewer owns only the cross-repository consistency check, and the README documents the merge order a human follows and the compatibility window between the two merges. One runner (warpdotdev/dev-go:1.23, Go 1.23 + Node 22) bootstraps both checkouts. Intake is a factory-ready label on an issue in either repository. Validation: - python3 scripts/validate_factory_files.py examples/25-related-services/: valid - python3 scripts/check_conventions.py: OK - python3 -m unittest discover -s scripts -p 'test_*.py': 12 tests OK - validator sweep over examples/*/: all valid Not applied against a live team. Co-Authored-By: Warp <agent@warp.dev>
![warp-agent-staging[bot]](https://avatars.githubusercontent.com/in/2196476?s=60&v=4){kind=small}
There was a problem hiding this comment.
The parser, convention checks and CI pass, but the contract-check sequence and single-repository handoff need correction before approval. Live Factory/app execution was not performed.
Responding as Docs Factory (V2): Open session · View in factory
There was a problem hiding this comment.
The previously reported issues are corrected; re-review found no remaining material findings. Parser and convention checks pass, and CI is green. Live Factory execution was not performed.
Responding as Docs Factory (V2): Open session · View in factory
|
This PR was generated with Warp, requested by @hongyi-chen. Comment    |
There was a problem hiding this comment.
Reviewed the full diff against current docs and repository guidance. No findings. Conventions, helper tests, and v1alpha1 parser checks pass; CI is green. Live apply and integration trials were not run.
Responding as Docs Factory (V2): Open session · View in factory
Why
Show safe coordination between an API provider and its consumer.
What
Verification
python3 scripts/check_conventions.pypassed;python3 -m unittest discover -s scripts -p 'test_*.py'passed (12 tests).The repository validator passed for all nine roots; the current bundled validator passed for the changed root; schema drift check:
v1alpha1.Validated with the warp-server parser for v1alpha1; state-dependent apply checks were not run.
No live apply, integration trial, or end-to-end factory run was performed.
Related merged-docs screenshots only; these do not demonstrate execution of this example.
Computer-use screenshots (6)
Port 4321 monorepo factory page: "Check shared dependencies and involve their owners" verification instructions with pnpm code block
Port 4322 Linear-to-pull-request page: "What comes back" section with claim-time state-handling wording
Port 4323 Testing and tuning your factory: "Tune one setting" heading, table and numbered tuning steps
Port 4323 Testing and tuning: "Test with a small change" trial instructions
Port 4321 testing page: single "Guide navigation" section with one intake list, followed by Related pages
Microservices guide "How a microservices factory is organized" section with four paragraphs and a summary table, rendered without overflow