feat: add full EE Game Structures (x64) support - #42
Merged
Conversation
4Luke4
marked this pull request as ready for review
August 24, 2026 12:05
4Luke4
marked this pull request as draft
August 24, 2026 13:05
4Luke4
marked this pull request as ready for review
August 24, 2026 13:44
Ingest the complete factual x64 layout dataset and expose member-aware completion, hover, definition, annotation, and chained type resolution. Automate commit-pinned EEex metadata refreshes, harden validation and repository workflows, reconcile label definitions, replace illustrative screenshots with verified VS Code captures, and coordinate the v0.4.0 release metadata. Replace the repetition-based type-normalization expressions identified by CodeQL with deterministic string scanning for qualifiers and pointers.
4Luke4
force-pushed
the
feat/ee-game-structures-x64
branch
from
August 24, 2026 14:52
83c82b6 to
5f5dcc2
Compare
4Luke4
marked this pull request as draft
August 24, 2026 14:53
4Luke4
marked this pull request as ready for review
August 24, 2026 14:54
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
This pull request adds full, permission-safe EE Game Structures (x64) layout support and completes the requested repository-maintenance work.
devrevision without hardcoded commit or subtree SHAsEnd-user experience
Fields do not pollute global completion. They appear when the receiver can be resolved as an x64 structure:
The same resolution works for
---@paramannotations and direct structure-qualified expressions such asCGameSprite.. Qualified pointer types such asconst struct CDerivedStats **are normalized safely for chained lookup.Completion uses the unqualified member name. Hover and resolved completion documentation display the qualified field, signature, type, offset, numeric or symbolic size, and an immutable source link. Definition navigation targets the exact line in the recorded upstream commit. For example,
CGameSpriteexposes all 339 parsed layout fields.“Full” here refers to the complete factual structure layouts and their editor behavior. Permission-gated narrative paragraphs are deliberately not bundled; the UI states that clearly and links to the source.
Automated EEex updates
The Update EEex API data workflow:
Bubb13/EEex-Docsdaily at 04:23 UTC and supports manual dispatchdevcommitnpm run verifygateGenerated symbols use commit-pinned, line-level provenance. The package audit rejects count drift, malformed fields, missing layout metadata, duplicate IDs, or permission-gated prose.
Workflow and label audit
The permanent workflows have distinct responsibilities; no redundant build/package workflow remains. CI validates changes, CodeQL performs security analysis, dependency review evaluates manifest changes, release re-verifies the selected release commit before packaging, and the remaining automation handles labeling, maintenance, and EEex data updates.
Only workflows that install npm dependencies use the npm cache. CI, release, and EEex regeneration explicitly key setup-node caching from
package-lock.json; metadata-only workflows do not create low-value caches.The labeler reconciles all labels it consumes from trusted base-branch definitions. Its JavaScript/TypeScript rule now covers
.js,.mjs,.cjs,.ts, and.tsx; the four required labels are present on this pull request.Documentation and release metadata
<details>sectionValidation
Final head
5f5dcc273694ee730e4cb117c14d8d3f31f8dc03:maindocumentation,dependencies,github_actions, andjavascriptconfirmed