Fix copy controls and add field exports - #34
Merged
Merged
Conversation
erinepshovel-code
marked this pull request as ready for review
August 3, 2026 06:28
erinepshovel-code
changed the title
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.
What changed
Repairs the deployment gate for the copy-control feature and extends every ordinary substantive field with one compact action group:
Linked cards retain sibling controls, avoiding nested interactive elements. Four Cuts uses the same controls.
Root cause
PR #33 added the copy script to both the public splash and the emergency fallback, while the established contracts require the fallback to contain no script. The splash contract was also still asserting no script, so the required build stopped before Pages could publish the merged feature.
Validation
npm test— 44/44 passedgit diff --check— passedhmmm
The emergency fallback deliberately remains copy-control-free because it must remain usable with no JavaScript or external dependencies. The local rendered-site build could not complete after an external textbook-refresh timeout; CI is the authoritative full build and browser gate.