feat(node): add node-forge contracts

[matiasdaloia]

Parent: #51

Depends on

• feat(node): wire contract resolver and KB plumbing #82

Working unit

Author Node callgraph contracts for node-forge, paired with existing rules.

Scope

• Inventory current detection-rule Node APIs for node-forge.
• Add schema-v2 YAML under internal/callgraph/contracts/node/.
• Record each API disposition in the PR body.
• Add focused embedded-KB assertions.

Out of scope

• No parser or resolver infrastructure changes.
• No unrelated Node libraries.

Acceptance criteria

• Node resolver/plumbing issue is merged.
• Every current rule API in scope has a disposition.
• go test ./internal/callgraph/contracts/... passes.

Dependency-intelligence contract acceptance

This issue owns library semantics. Shared export behavior is covered by #116 and #117.

Where the library API exposes the corresponding semantics:

• Classify lifecycle methods with the contract-native roles factory, config, operation, and output (config represents configuration).
• Record parameter roles and supported derivations for arguments that select an operation or contribute crypto metadata.
• Resolve interface, trait, or inherited lifecycle roles to concrete callable identities where the language supports it.
• Add focused embedded-KB assertions for every authored lifecycle role and parameter derivation.
• Keep parameter-condition syntax in detection rules; do not add forward-call or runtime-provider routing fields to contract YAML.

[matiasdaloia]

This was generated by AI during triage.

Blocker reconciliation: #82 is closed and its implementation PR is merged. All declared blockers are now complete, so this issue is ready for agent work.