Fix declaration emit dropping readonly from as const object literal properties

[Copilot]

• Inspect current branch status and recent workflow runs
• Fetch full history and merge latest origin/main
• Resolve baseline merge conflict
• Refresh affected baselines
• Run targeted declaration emit tests
• Run required validation commands
• Run parallel code review and CodeQL validation
• Reply to actionable PR comment with addressing commit hash

[Copilot]

Pull request overview

Fixes a declaration emit regression in the Go port where as const object literals could lose readonly on all properties when the first property was a method shorthand, by ensuring const-context detection starts from the object literal node rather than the first property’s name.

Changes:

• Update pseudo type node building to compute isConst from the containing ObjectLiteralExpression (so method shorthands don’t break const-context propagation).
• Add a new compiler test + reference baselines covering as const with a method shorthand and nested object property.
• Update an existing reference baseline (declarationEmitConstObjectLiteralGenericMethod1) to reflect correct readonly + function-type property emission for const object literal methods.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
internal/checker/pseudotypenodebuilder.go	Fixes const-context detection for pseudo object literal emission by anchoring the check at the object literal node.
testdata/tests/cases/compiler/declarationEmitReadonlyAsConst.ts	Adds regression test reproducing the missing-readonly behavior with a leading method shorthand.
testdata/baselines/reference/compiler/declarationEmitReadonlyAsConst.types	Reference type baseline for the new test.
testdata/baselines/reference/compiler/declarationEmitReadonlyAsConst.symbols	Reference symbol baseline for the new test.
testdata/baselines/reference/compiler/declarationEmitReadonlyAsConst.js	Reference JS + .d.ts baseline verifying readonly properties and function-type method emission.
testdata/baselines/reference/compiler/declarationEmitConstObjectLiteralGenericMethod1.js	Updates .d.ts reference output to match corrected readonly/function-type emission for const object literal generic methods.

[weswigham]

Yep, this looks right - there was just a logic error mismatch between what isConstContext checks and what it was expected to check. It doesn't flow const-ness down into names of declarations, rather it only checks the expression itself, so we need to walk up from name -> member -> expression.

[jakebailey]

@copilot merge main and resolve conflicts and update baselines

[Copilot]

@copilot merge main and resolve conflicts and update baselines

Merged origin/main, resolved the baseline conflict, refreshed baselines, and reran validation. Addressed in f8bb62d (merge commit 25851eb).

[weswigham]

Aside: methods and function-typed members have different behavior - adding readonly swapping which one we printback is... probably a very subtle error (say it with me: "function argument bivariance"). We probably need to support readonly on methods properly to fix that.