Repository navigation
glc-launch docs: Group Policy is the deployment route - #202
Merged
Merged
Conversation
The handler is approved as designed (no path allow-list) and deployed by the system administrator through Group Policy: HKLM registration, script under C:\Program Files\AAAC\, no -ExecutionPolicy switch (a GPO-set policy overrides it; sign the script instead). glc-protocol.reg is kept for stand-alone PCs only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MEMWFFUqqy3KcvGhdY9tuk
Contributor
|
📄 DITA-OT preview — full corpus, rebuilt from
It carries no stylesheet — that is deliberate. It is here to check content, filtering and structure. 🎨 Oxygen sample — the design surface, and the only place theme changes are visible:
Nine gram pages from Rebuilt on every push to this PR; removed when the PR closes. (May take a minute for GitHub Pages to 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
2 participants
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.
Follow-up to #201. This brings the repo's
.glchandler docs in line with the decision recorded on #199: Decision A, approved as designed with no folder restriction, deployed by the system administrator through Group Policy.Changes (docs and comments only, no code behaviour change)
theme/glc-launch/README.md:C:\Program Files\AAAC\and item-level targeting.-ExecutionPolicy, so the command carries none; sign the script instead), the browser prompt (AutoLaunchProtocolsFromOrigins, untested forfile://), and a pointer to the accepted risks on Should open .glc file, not display it #199..regroute is kept as stand-alone PCs only.client/glc-protocol.reg: header now says stand-alone only, and explains why-ExecutionPolicy Bypassstays there.client/glc-launch.ps1: header comment names both registration routes.README.md: the operator note now points at Group Policy deployment.Validation
python -m unittest tests.test_package_releasepasses. Both client files keep their CRLF line endings.🤖 Generated with Claude Code
https://claude.ai/code/session_01MEMWFFUqqy3KcvGhdY9tuk
Generated by Claude Code