GitHub-native artifact fallback: refs travel as issue comments when Notion is absent#44
Merged
Merged
Conversation
Real-world gap from the first bloom-mono epic run: with Notion unconfigured, publish dropped to 'GitHub + local only' and a remote /do would get the issue body with none of the discussion/research refs. Now degraded publish posts each ref as a marker-delimited issue comment and /do Step 0 reconstructs ./tmp/<id>/refs/ from them. Co-Authored-By: Claude Fable 5 <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.
Summary
First real Orchestra run (bloomapi/bloom-mono epic) hit this: Notion wasn't configured, publish degraded to "GitHub + local only", and the refs (discussion log, code research) existed only in local ./tmp/. A remote agent running /do <issue#> would plan from the bare issue body — no prior context.
Fix, additive:
<!-- ORCHESTRA-ARTIFACT path="..." -->markers (part=n splits for oversized files). The issue becomes self-contained.This was the "issue-marker reconstruction" idea deferred in the substance-loss audit as "Notion is the channel" — the first unconfigured machine proved the channel needs a fallback.
🤖 Generated with Claude Code