Mission R: fix stale froggyPipeline render + purge DAG-orchestration docs - #11
Merged
Merged
Conversation
…tion docs (Mission R)
Forward-only residue eradication. Zero behavior change to valid current output.
- src/afiCli.ts: `/afi reactor status` rendered `Froggy Pipeline: ${result.froggyPipeline}`
but the reactor /health response returns {status, service, composition} and has NO
froggyPipeline field, so it printed "Froggy Pipeline: undefined". Now renders the real
`Composition: ${result.composition}` field.
- src/afiClient.ts: HealthCheckResponse now declares the real `service`/`composition`
fields (previously only reachable via the index signature).
- Delete stale docs: docs/MODEL_PROVIDER_FIX.md + docs/INTEGRATION_COMPLETE_SUMMARY.md
("Historical snapshot" banners) + docs/AFI_REACTOR_INTEGRATION.md (obsolete 6-stage
froggyPipeline integration tutorial with dead links to the deleted
afi-reactor/src/config/froggyPipeline.ts).
- Correct stale "DAG orchestration" labels + a dead froggyPipeline.ts link in README.md,
plugins/afi-reactor-actions/README.md, and the agent docs (checklist/playbook/character)
to the current manifest-driven pipeline runtime + governed afi-config registries.
Note: legitimate "Froggy" references (the CURRENT registered strategy/graph
froggy-trend-pullback v1.1.0 + runFroggyTrendPullback client) are preserved — only the
deleted `froggyPipeline` field/file and DAG-orchestration framing were removed.
Proof: tsc --noEmit clean; jest 56 pass / 0 fail.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
…ctor main (Mission R)
The Gateway->Reactor boundary proof pinned afi-reactor at d1e5a1f (pre-Mission-B),
which predates the froggy-trend-pullback@v1.1.0 five-lane pipeline that afi-config
main now registers -> the old pinned reactor could not resolve the current registry
composition ('not a registered pipeline', D-FCP-8 honest boot refusal). Bumped the
pin to the current reactor main (2a06c82), which supports v1.1.0 (proven by the
reactor's own green CI). Stale-pin residue; unrelated to the CLI/doc fixes.
Co-Authored-By: Claude Opus 4.8 (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
1 participant
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.
Forward-only residue eradication (AFI Mission R). Zero change to valid current output.
Code fix
src/afiCli.ts—/afi reactor statusrenderedFroggy Pipeline: ${result.froggyPipeline}; the reactor/healthreturns{status, service, composition}(nofroggyPipeline), so it printedundefined. Now renders the realComposition: ${result.composition}.src/afiClient.ts—HealthCheckResponsenow declares the realservice/compositionfields.Docs
docs/MODEL_PROVIDER_FIX.md+docs/INTEGRATION_COMPLETE_SUMMARY.md("Historical snapshot" banners) +docs/AFI_REACTOR_INTEGRATION.md(obsolete froggyPipeline integration tutorial; dead links to the deletedfroggyPipeline.ts).froggyPipeline.tslink inREADME.md,plugins/afi-reactor-actions/README.md, and 3 agent docs → current manifest-driven pipeline runtime + governed afi-config registries.Legitimate Froggy references (the current
froggy-trend-pullbackv1.1.0 strategy/graph +runFroggyTrendPullbackclient) are preserved.Proof:
tsc --noEmitclean; jest 56 pass / 0 fail.🤖 Generated with Claude Code