chore: remove root pickled.yml#3601
Merged
Merged
Conversation
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
No issues found across 1 file
Tip: cubic could auto-approve low-risk PRs like this, if it thinks it's safe to merge. Learn more
Re-trigger cubic
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.
Pickled's config schema changed: the published CLI moved to a new product / sources / agents / access / questions / checks model, and the runtime trap concept was removed. The existing root
pickled.ymlis on the old schema, so it now breaks onbunx @pickled-dev/cli@latest.Removing it rather than rushing a migration. A stale or half-thought config teaches the wrong workflow and is worse than no config. The SuperDoc agent-legibility suite will be reintroduced as a small, deliberate set focused on public agent context once those questions and source surfaces are finalized.
The learnings from the first pass (docs vs llms.txt vs web vs MCP reach, React UI provider visibility, Document API vs React UI confusion) are kept as notes for that reintroduction.