Fix Potential Buffer Overflow

[Lightning11wins]

Fix a potential buffer overflow in wgtr.c.

[greptile-apps]

Greptile Summary

This PR fixes a copy-paste error in wgtrNewNode where strtcpy(node->Type, type, sizeof(node->Name)) used the size of Name instead of Type as the buffer bound. Both WgtrNode.Type and WgtrNode.Name are currently char[64], so no overflow was occurring, but the fix correctly aligns the size argument with the destination field, guarding against any future struct layout changes.

Confidence Score: 5/5

This PR is safe to merge — it is a minimal, correct bug fix with no adverse side effects.

Single-line change correcting the wrong sizeof argument in a strtcpy call. Both fields are currently the same size (char[64]), so there is no existing overflow; the fix removes a latent hazard and improves correctness. No new logic, no regressions, no security concerns.

No files require special attention.

Important Files Changed

Filename	Overview
centrallix/wgtr/wgtr.c	Single-line fix: corrects sizeof(node->Name) → sizeof(node->Type) in strtcpy call for node->Type. Both fields happen to be char[64], so no real overflow was occurring, but the fix removes a latent risk if field sizes ever diverge.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["wgtrNewNode(name, type, ...)"] --> B["nmMalloc / memset / SETMAGIC"]
    B --> C["strtcpy(node->Name, name, sizeof(node->Name))"]
    C --> D["strtcpy(node->Type, type, sizeof(node->Type))\n✅ fixed (was sizeof(node->Name))"]
    D --> E["snprintf(node->DName, ...)"]
    E --> F["Set geometry & other fields"]
    F --> G["Return pWgtrNode"]

Loading

_{Reviews (2): Last reviewed commit: "Fix a potential buffer overflow bug." | Re-trigger Greptile}

[Lightning11wins]

PR cleared for human review.

[Lightning11wins]

Redefining the scope on this since I've changed my methodology and no longer think trying to cluster unrelated fixes into a single PR is a good idea.

[Lightning11wins]

Once again, this PR is still cleared for human review.