test: restore coverage of the unreadable status.yaml FILE branch (spec 146)

[pseudoseed]

Two code paths reach STATUS_UNREADABLE and only one was covered.

readScopedStatus maps EACCES/EPERM from reading the file; readStatusesFromArtifactRoot maps it from reading the projects directory. The single existing test covered only the directory, leaving the file branch free to collapse into STATUS_MALFORMED — reporting a permissions problem as a corrupt file. Different diagnosis, different fix.

Verified before writing the test: disabling the file-level EACCES/EPERM branch left all 3619 agent-farm tests passing.

This is a regression, not an original gap

The test once chmod'd the status file and called readScopedStatus. Later order-safe and skip as root refactors moved the target to the directory while keeping the name.

A test that moves to a different code path while keeping its name is worse than no test, because it reads as coverage. So there are now two tests whose names say which path each one holds.

Mutation-verified, and each kills only its own test

Branch disabled	Test that fails	Failure
file-level EACCES/EPERM	unreadable status.yaml FILE	expected STATUS_MALFORMED to be STATUS_UNREADABLE
directory-level	unreadable projects DIRECTORY	expected [] to equal [ObjectContaining]

Neither mutation touches the other test, so the two paths cannot collapse into one another again.

Scope

Test file only — status-reader.ts is unchanged. The root skip is kept on both tests so neither can pass spuriously. Standalone against main rather than folded into phase 6, so a one-test fix does not wait on a phase.

🤖 Generated with Claude Code

[pseudoseed]

Two code paths reach STATUS_UNREADABLE and only one was covered.

readScopedStatus maps EACCES/EPERM from reading the file; readStatusesFromArtifactRoot maps it from reading the projects directory. The single existing test covered only the directory, leaving the file branch free to collapse into STATUS_MALFORMED — reporting a permissions problem as a corrupt file. Different diagnosis, different fix.

Verified before writing the test: disabling the file-level EACCES/EPERM branch left all 3619 agent-farm tests passing.

This is a regression, not an original gap

The test once chmod'd the status file and called readScopedStatus. Later order-safe and skip as root refactors moved the target to the directory while keeping the name.

A test that moves to a different code path while keeping its name is worse than no test, because it reads as coverage. So there are now two tests whose names say which path each one holds.

Mutation-verified, and each kills only its own test

Branch disabled	Test that fails	Failure
file-level EACCES/EPERM	unreadable status.yaml FILE	expected STATUS_MALFORMED to be STATUS_UNREADABLE
directory-level	unreadable projects DIRECTORY	expected [] to equal [ObjectContaining]

Neither mutation touches the other test, so the two paths cannot collapse into one another again.

Scope

Test file only — status-reader.ts is unchanged. The root skip is kept on both tests so neither can pass spuriously. Standalone against main rather than folded into phase 6, so a one-test fix does not wait on a phase.

🤖 Generated with Claude Code

[pseudoseed]

Two code paths reach STATUS_UNREADABLE and only one was covered.

readScopedStatus maps EACCES/EPERM from reading the file; readStatusesFromArtifactRoot maps it from reading the projects directory. The single existing test covered only the directory, leaving the file branch free to collapse into STATUS_MALFORMED — reporting a permissions problem as a corrupt file. Different diagnosis, different fix.

Verified before writing the test: disabling the file-level EACCES/EPERM branch left all 3619 agent-farm tests passing.

This is a regression, not an original gap

The test once chmod'd the status file and called readScopedStatus. Later order-safe and skip as root refactors moved the target to the directory while keeping the name.

A test that moves to a different code path while keeping its name is worse than no test, because it reads as coverage. So there are now two tests whose names say which path each one holds.

Mutation-verified, and each kills only its own test

Branch disabled	Test that fails	Failure
file-level EACCES/EPERM	unreadable status.yaml FILE	expected STATUS_MALFORMED to be STATUS_UNREADABLE
directory-level	unreadable projects DIRECTORY	expected [] to equal [ObjectContaining]

Neither mutation touches the other test, so the two paths cannot collapse into one another again.

Scope

Test file only — status-reader.ts is unchanged. The root skip is kept on both tests so neither can pass spuriously. Standalone against main rather than folded into phase 6, so a one-test fix does not wait on a phase.

🤖 Generated with Claude Code

[pseudoseed]

Two code paths reach STATUS_UNREADABLE and only one was covered.

readScopedStatus maps EACCES/EPERM from reading the file; readStatusesFromArtifactRoot maps it from reading the projects directory. The single existing test covered only the directory, leaving the file branch free to collapse into STATUS_MALFORMED — reporting a permissions problem as a corrupt file. Different diagnosis, different fix.

Verified before writing the test: disabling the file-level EACCES/EPERM branch left all 3619 agent-farm tests passing.

This is a regression, not an original gap

The test once chmod'd the status file and called readScopedStatus. Later order-safe and skip as root refactors moved the target to the directory while keeping the name.

A test that moves to a different code path while keeping its name is worse than no test, because it reads as coverage. So there are now two tests whose names say which path each one holds.

Mutation-verified, and each kills only its own test

Branch disabled	Test that fails	Failure
file-level EACCES/EPERM	unreadable status.yaml FILE	expected STATUS_MALFORMED to be STATUS_UNREADABLE
directory-level	unreadable projects DIRECTORY	expected [] to equal [ObjectContaining]

Neither mutation touches the other test, so the two paths cannot collapse into one another again.

Scope

Test file only — status-reader.ts is unchanged. The root skip is kept on both tests so neither can pass spuriously. Standalone against main rather than folded into phase 6, so a one-test fix does not wait on a phase.

🤖 Generated with Claude Code

[pseudoseed]

Two code paths reach STATUS_UNREADABLE and only one was covered.

readScopedStatus maps EACCES/EPERM from reading the file; readStatusesFromArtifactRoot maps it from reading the projects directory. The single existing test covered only the directory, leaving the file branch free to collapse into STATUS_MALFORMED — reporting a permissions problem as a corrupt file. Different diagnosis, different fix.

Verified before writing the test: disabling the file-level EACCES/EPERM branch left all 3619 agent-farm tests passing.

This is a regression, not an original gap

The test once chmod'd the status file and called readScopedStatus. Later order-safe and skip as root refactors moved the target to the directory while keeping the name.

A test that moves to a different code path while keeping its name is worse than no test, because it reads as coverage. So there are now two tests whose names say which path each one holds.

Mutation-verified, and each kills only its own test

Branch disabled	Test that fails	Failure
file-level EACCES/EPERM	unreadable status.yaml FILE	expected STATUS_MALFORMED to be STATUS_UNREADABLE
directory-level	unreadable projects DIRECTORY	expected [] to equal [ObjectContaining]

Neither mutation touches the other test, so the two paths cannot collapse into one another again.

Scope

Test file only — status-reader.ts is unchanged. The root skip is kept on both tests so neither can pass spuriously. Standalone against main rather than folded into phase 6, so a one-test fix does not wait on a phase.

🤖 Generated with Claude Code

[pseudoseed]

Two code paths reach STATUS_UNREADABLE and only one was covered.

readScopedStatus maps EACCES/EPERM from reading the file; readStatusesFromArtifactRoot maps it from reading the projects directory. The single existing test covered only the directory, leaving the file branch free to collapse into STATUS_MALFORMED — reporting a permissions problem as a corrupt file. Different diagnosis, different fix.

Verified before writing the test: disabling the file-level EACCES/EPERM branch left all 3619 agent-farm tests passing.

This is a regression, not an original gap

The test once chmod'd the status file and called readScopedStatus. Later order-safe and skip as root refactors moved the target to the directory while keeping the name.

A test that moves to a different code path while keeping its name is worse than no test, because it reads as coverage. So there are now two tests whose names say which path each one holds.

Mutation-verified, and each kills only its own test

Branch disabled	Test that fails	Failure
file-level EACCES/EPERM	unreadable status.yaml FILE	expected STATUS_MALFORMED to be STATUS_UNREADABLE
directory-level	unreadable projects DIRECTORY	expected [] to equal [ObjectContaining]

Neither mutation touches the other test, so the two paths cannot collapse into one another again.

Scope

Test file only — status-reader.ts is unchanged. The root skip is kept on both tests so neither can pass spuriously. Standalone against main rather than folded into phase 6, so a one-test fix does not wait on a phase.

🤖 Generated with Claude Code

[pseudoseed]

Two code paths reach STATUS_UNREADABLE and only one was covered.

readScopedStatus maps EACCES/EPERM from reading the file; readStatusesFromArtifactRoot maps it from reading the projects directory. The single existing test covered only the directory, leaving the file branch free to collapse into STATUS_MALFORMED — reporting a permissions problem as a corrupt file. Different diagnosis, different fix.

Verified before writing the test: disabling the file-level EACCES/EPERM branch left all 3619 agent-farm tests passing.

This is a regression, not an original gap

The test once chmod'd the status file and called readScopedStatus. Later order-safe and skip as root refactors moved the target to the directory while keeping the name.

A test that moves to a different code path while keeping its name is worse than no test, because it reads as coverage. So there are now two tests whose names say which path each one holds.

Mutation-verified, and each kills only its own test

Branch disabled	Test that fails	Failure
file-level EACCES/EPERM	unreadable status.yaml FILE	expected STATUS_MALFORMED to be STATUS_UNREADABLE
directory-level	unreadable projects DIRECTORY	expected [] to equal [ObjectContaining]

Neither mutation touches the other test, so the two paths cannot collapse into one another again.

Scope

Test file only — status-reader.ts is unchanged. The root skip is kept on both tests so neither can pass spuriously. Standalone against main rather than folded into phase 6, so a one-test fix does not wait on a phase.

🤖 Generated with Claude Code

[pseudoseed]

Two code paths reach STATUS_UNREADABLE and only one was covered.

readScopedStatus maps EACCES/EPERM from reading the file; readStatusesFromArtifactRoot maps it from reading the projects directory. The single existing test covered only the directory, leaving the file branch free to collapse into STATUS_MALFORMED — reporting a permissions problem as a corrupt file. Different diagnosis, different fix.

Verified before writing the test: disabling the file-level EACCES/EPERM branch left all 3619 agent-farm tests passing.

This is a regression, not an original gap

The test once chmod'd the status file and called readScopedStatus. Later order-safe and skip as root refactors moved the target to the directory while keeping the name.

A test that moves to a different code path while keeping its name is worse than no test, because it reads as coverage. So there are now two tests whose names say which path each one holds.

Mutation-verified, and each kills only its own test

Branch disabled	Test that fails	Failure
file-level EACCES/EPERM	unreadable status.yaml FILE	expected STATUS_MALFORMED to be STATUS_UNREADABLE
directory-level	unreadable projects DIRECTORY	expected [] to equal [ObjectContaining]

Neither mutation touches the other test, so the two paths cannot collapse into one another again.

Scope

Test file only — status-reader.ts is unchanged. The root skip is kept on both tests so neither can pass spuriously. Standalone against main rather than folded into phase 6, so a one-test fix does not wait on a phase.

🤖 Generated with Claude Code