docs(agents): discuss upstream features that duplicate Pylon's own - #431
Merged
Conversation
Preserving Pylon behavior is the right default for adaptations and conflicts, but it should not silently decide a feature Pylon and upstream both built. Record the maintainer's standing preference: surface the overlap, compare on merits, and be willing to take upstream's implementation and delete Pylon's when theirs is better.
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
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.
The upstream review skill told agents to preserve Pylon behavior, with no guidance for the case where upstream independently ships something Pylon already built. That default silently resolves a question the maintainer wants to answer, and the source tends to get filed as "already covered" without anyone comparing the two implementations.
Records the standing preference in both places an agent reads: a boundary bullet in
SKILL.mdand a scope row in the decision framework. Neither version wins by default — surface the overlap, compare on merits, and treat adopting upstream's implementation and deleting Pylon's as a legitimate outcome. Preservation stays the default for adaptations and conflicts.Instructions only; no product code, source disposition, review cursor or Git ancestry changes. Table reflow in the framework is the formatter realigning columns for the new row.
Model: Claude Opus 5 (1M context), harness: Pylon / Claude Code.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.