Repository navigation
docs(prds): renumber the low-resolution temporal PRD to 539 - #467
Merged
Merged
Conversation
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.
TL;DR: #398 filed its follow-up PRD as PRD-537. #464 landed a different PRD-537 (far hills) first, so develop now has two files with that number. This renames mine to PRD-539 and repoints every reference. No behaviour change.
docs/PRDs/rendering/PRD-537-low-resolution-temporal-reconstruction-quality-and-cost.mdtoPRD-539-…, with a numbering note in its header.integration.yml.Evidence:
pnpm check:docs(2,543 links), andcheck-doc-links,evidence-citations,sync-agent-docs,ci-structure,ci-needsspecs all pass (235 tests).Follows #398 (merged as
f1040a1cf).