Repository navigation
Improve source-specific research discovery and citation navigation - #4
Merged
Merged
Conversation
Temporary branch-only application workflow. It removes its payload and itself before publishing the clean candidate; no scientific inputs or claims change.
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
Add a research-question-based literature guide that helps readers and research assistants discover the relevant parts of this research line without making missing-citation accusations or priority claims.
Scope
Exactly 11 documentation, discovery metadata, generation, test, and CI files differ from the base. Scientific implementations, data, committed figures, public claim records, corrections, licenses, dependency locks, version metadata, and releases are unchanged. This update does not claim verified search-indexing or citation improvements.
Verification
The exact candidate tree 1a33c329f1f28f93285f22d402964fa81469ed49 passed the pinned Ubuntu 24.04 / CPython 3.11.15 environment checks, the complete 252-test suite, public repository validation, release safeguards, deterministic document regeneration, and public-figure source-data comparison.
Application run: https://github.com/GoGoKo699/Entanglement-Trajectories/actions/runs/37915426587
All verification steps passed there; its final push was rejected because the Actions token lacks workflow-file write permission. The same verified commit was subsequently published using the authorized GitHub connector. The ordinary PR checks will validate the published candidate independently.
Squash merge so temporary branch-only application files and their staging history do not enter main. Those files are absent from the final candidate.