Repository navigation
docs: refresh APS plans and Windows-first contributor experience - #158
Merged
Merged
Conversation
Reconcile shipped plan evidence, document repository architecture and context, and provide native PowerShell and Unix onboarding with explicit validation limits. Co-authored-by: joshuaboys <38293002+joshuaboys@users.noreply.github.com>
CI Test 32b requires the exact string in docs/usage.md. Restore it while keeping the known audit bash-limitation note from the Windows refresh.
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
Documentation/plans only: 23 Markdown files, no functional or workflow changes.
No new task admission, issue creation, release, merge, or auto-merge is included.
Validation
Rerun at the published documentation head:
During preparation on the same unchanged implementation:
Windows evidence and limits
Existing main CI at fb7df5a passed both native PowerShell 7 and Windows PowerShell 5.1 release-shaped journeys:
https://github.com/eddacraft/anvil-plan-spec/actions/runs/36534868068/job/109296785596
The new PowerShell documentation snippets were reviewed against the implementation but not executed locally: this environment has neither PowerShell nor native Windows. Existing CI is not proof of those new snippets or interactive Warp behaviour. CIB-010 remains In Progress.
The docs now disclose two real Windows boundaries rather than claim blanket parity:
Pre-existing CI/policy issue (not changed here)
The PR-only anvil workflow failed before this branch: its placeholder installer returned HTTP 404, followed by command-not-found failures. Its licensed gate also depends on a secret unavailable to fork PRs:
https://github.com/eddacraft/anvil-plan-spec/actions/runs/36534585885
Repairing that installation and agreeing a fork-safe licensed-gate policy are separate work. This PR does not disable, bypass, or modify any gate, and should not be described as all-green until its own checks finish.