Conversation
…al-API findings OC #85 + ER #6 landed the Archon real-workflow integration on 2026-05-07. Same-day live validation against a built-from-source container surfaced three findings; this PR folds them back into the canonical docs. archon-real-workflow-integration.md: - Status: "Approved design — implementation pending" → "Shipped 2026-05-07" with PR refs. - Workflow-name table corrected to the real bundled defaults Archon ships (archon-assist / archon-fix-github-issue / archon-test-loop-dag / archon-refactor-safely). Earlier-draft archival note kept inline so history is visible. - New "Real-API findings (2026-05-07 live validation)" section near the bottom documenting F1 (workflow-name divergence, now fixed in OC), F2 (/api/workflows is cwd-scoped — empty without ?cwd= linking to a registered codebase), F3 (kickoff returns 200 + {accepted,status: "started"} — confirms the AsyncHttpRunner upgrade was correct). - "What's still outstanding" pulled out of "Out of scope" so it reads as forward-looking rather than retrospective. archon-setup.md: - "deferred" / "health-only probe" wording → "shipped" wording with cross-link to the design doc + Real-API findings section. - runtime_kind documented as http_async (production path); ABC + ManualRunner closure path noted as test-only. - --list-workflows usage documented including the expected "no workflows returned" signal against a fresh container (cwd-scoped discovery; not a bug). - Deferred section refreshed: auto-approve policy, SSE streaming, and the new --cwd flag enhancement on the operator probe. No code changes in this PR; OC's commit (chore/archon-defaults-from-real-archon) ships the matching DEFAULT_WORKFLOW_NAMES correction and tests. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
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.
Summary
OC #85 + ER #6 landed the Archon real-workflow integration on 2026-05-07. Same-day live validation against a built-from-source container surfaced three findings; this PR folds them back into the canonical docs.
Changes
docs/architecture/adapters/archon-real-workflow-integration.mdarchon-assist,archon-fix-github-issue,archon-test-loop-dag,archon-refactor-safely. Earlier-draft archival note kept inline so history is visible. The matching code change ships in Velascat/OperationsCenter#TBD./api/workflowsis cwd-scoped: empty without?cwd=linking to a registered codebase. Dispatch-by-name still works.{accepted, status:"started"}exactly as the AsyncHttpRunner upgrade predicted.docs/operations/archon-setup.mdruntime_kinddocumented ashttp_async(production path); ABC + ManualRunner closure path noted as test-only.--list-workflowsusage documented including the expected "no workflows returned" signal against a fresh container (cwd-scoped discovery; not a bug).--cwdflag enhancement on the operator probe.Test plan
🤖 Generated with Claude Code