Repository navigation
Conversation
Sets up a Cursor Cloud Agent development environment: - install: adds segno (the only third-party dep, used by the docs/statements generators; the rest of the tooling is stdlib-only) - terminals: serves the Network Activity Statement gallery on :8000 for local preview of generated client/operator statements - ports: exposes 8000 Co-authored-by: David Allum <a777ance@gmail.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
cloudflarelocaldns | 0d2275c | Sep 12 2026, 03:05 AM |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
.cursor/environment.jsonso this repo is fully usable in Cursor Cloud Agents. Repo-managed (versioned with code, follows branches/PRs) and highest-precedence environment source, so merging this PR is what activates it for future agents.Why
localDNS is an Infrastructure-as-Code snapshot whose "applications" are Python tooling:
tools/check-docs.py,tools/check-provenance.py,tools/check-doctrine.py— the repo's lint/test, gated at commit time by.claude/hooks/gate.sh.docs/statements/tools/generate_client.py,generate_operator.py) — the one place a third-party dependency,segno, is needed (matches the Pages CI in.github/workflows/pages.yml).04-user-services/ai-orchestration/jury/jury.py) — stdlib only, with an offline--mockmode.Config
install—pip install segno(the only external dependency; everything else is Python 3.12 stdlib). Idempotent.terminals— serves the Network Activity Statement gallery (docs/statements/) on:8000for local preview of generated statements.ports— exposes8000.Validation (this VM)
check-docs.py/check-provenance.py/check-doctrine.pygenerate_client.py+generate_operator.pydeliberate+calibrate(--mock):8000)Build-test (fresh Cloud Agent)
Draft build
bld-20260912-1595455b-1163-4d1e-8422-7d342389569cSUCCEEDED (install exit 0). A fresh Cloud Agent booted from that exact build on this branch re-verified:segno 1.6.6importable--mock)The
terminalsgallery server auto-launches for a real agent on the merged branch (repo-file managed). It was not auto-started in the draft-build verification pod only because a draft build'senvironmentJsonoverride recordsinstall/snapshot(notterminals); the command itself returns HTTP 200 on both the original VM and the fresh agent.Note
tools/sync-briefings.pyreports drift only because the cloud checkout dir is namedworkspacerather thanlocalDNS; the script self-excludes the repo by directory name, so it mistakes the repo for a sibling. Checkout-path artifact, not a repo defect, unrelated to this change.