zeekayandGitHub 8ffe80cfae chore(cli): kill subnet — zero subnet/Subnet/SUBNET in cli (#41) ...

Final lux sweep. Five small touches:

  cmd/networkcmd/start_local.go    "subnet creation" → "chain creation" (comment)
  cmd/explorecmd/explore.go        "or subnet name" → "or chain name" (flag help)
  pkg/plugins/luxdConfig_test.go   test fixture: testSubNet → testChain, subNetId000 → chainId000
  pkg/mpc/deploy.go                AWSSubnet → AWSNet (Go field + json tag)

The AWS field rename is Go-side only. AWS itself still calls the
resource a subnet on the wire; our config field carries the canonical
name without taking a dependency on AWS API verbiage.

Build clean.

2026-05-29 21:43:22 -07:00

..

backup.go

fix: add GOWORK/CGO env to all CI workflows and fix go fmt

2026-01-28 10:21:23 -08:00

deploy.go

chore(cli): kill subnet — zero subnet/Subnet/SUBNET in cli (#41)

2026-05-29 21:43:22 -07:00

node.go

fix: add GOWORK/CGO env to all CI workflows and fix go fmt

2026-01-28 10:21:23 -08:00

proc_unix.go

Fix Windows build: platform-specific process handling

2026-01-26 17:13:37 -08:00

proc_windows.go

Fix Windows build: platform-specific process handling

2026-01-26 17:13:37 -08:00