Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

instr/parse.go (1)

151-154: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Prefer errors.Is over string matching for the scanner error.

strings.Contains(err.Error(), "token too long") is fragile compared to checking against the exported bufio.ErrTooLong sentinel error with errors.Is.

♻️ Proposed fix

 import (
 	"bufio"
+	"errors"
 	"fmt"
 	"io"
 	"math"
 	"strconv"
 	"strings"
 )
 ...
 	if err := scanner.Err(); err != nil {
-		if strings.Contains(err.Error(), "token too long") {
+		if errors.Is(err, bufio.ErrTooLong) {
 			return nil, fmt.Errorf("line %d exceeds maximum allowed size of %d bytes", line, maxParseLineBytes)
 		}
 		return nil, err
 	}

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@instr/parse.go` around lines 151 - 154, The scanner error check in parse
logic relies on string matching, which should be replaced with the exported
sentinel error check. Update the error handling around the line-size validation
in the parsing flow to use errors.Is against bufio.ErrTooLong instead of
strings.Contains(err.Error(), "token too long"), while keeping the existing
wrapped message for the oversized line case and preserving the fallback return
of the original error.

program/parse.go (1)

39-42: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Same fragile string match for scanner error, occurring twice in this file.

Both scan phases detect the oversized-line condition via strings.Contains(err.Error(), "token too long"). Use errors.Is(err, bufio.ErrTooLong) instead, which is more robust and idiomatic for this stdlib sentinel error.

♻️ Proposed fix

 import (
 	"bufio"
+	"errors"
 	"fmt"
 	"io"
 	"strings"

 	"github.com/siyul-park/minivm/instr"
 	"github.com/siyul-park/minivm/types"
 )
 ...
 	if err := scanner.Err(); err != nil {
-		if strings.Contains(err.Error(), "token too long") {
+		if errors.Is(err, bufio.ErrTooLong) {
 			return nil, fmt.Errorf("line %d exceeds maximum allowed size of %d bytes", lineNum+1, maxParseLineBytes)
 		}
 		return nil, err
 	}
 ...
 	if err := scanner.Err(); err != nil {
-		if strings.Contains(err.Error(), "token too long") {
+		if errors.Is(err, bufio.ErrTooLong) {
 			return nil, fmt.Errorf("line %d exceeds maximum allowed size of %d bytes", lineNum+1, maxParseLineBytes)
 		}
 		return nil, err
 	}

Also applies to: 84-87

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@program/parse.go` around lines 39 - 42, The oversized-line handling in
parse.go is using a fragile string check for the scanner error in both scan
phases. Update the error handling in the relevant parsing logic around the
scanner/line processing paths to use errors.Is with bufio.ErrTooLong instead of
strings.Contains(err.Error(), "token too long"), and apply the same change
wherever this check appears in the file so the behavior stays consistent.