FA-9871 / Packaging / Open access

Package file manifest selection: Forced files override hard prohibitions · case 01

Forced files override hard prohibitions.

Verified by executionVariant 1 · 6 checks per implementationDownload source bundle ↓JSON ↗

ROOT CAUSE

The implementation substitutes pass for names -= set(forbidden), so forced files override hard prohibitions.

THE FAILURE

The implementation substitutes pass for names -= set(forbidden), so forced files override hard prohibitions.

Unsuccessful approach: The attempted repair substitutes names -= set(forbidden) - set(forced). Fixture 5 still yields ['a', 'b'] instead of ['a'].

Case contract

Include declared files, exclude forbidden files, retain force-included files despite ordinary exclusions, never include missing files, and sort unique names. Force cannot override forbidden.

Why this case matters

An offline model of package file manifest selection, suitable for testing build and release tooling without external services.

1 / The failure

Exit 1

"""Failure Map reference implementation. Python standard library only."""
import json

N = 1
observations = []
def solve(available, declared, excluded, forced, forbidden):
    names = (set(declared) - set(excluded)) | set(forced)
    names &= set(available)
    pass
    return sorted(names)
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('fixture 1', solve([], [], [], [], []), [])
check('fixture 2', solve(['a', 'b'], ['a', 'b'], ['b'], [], []), ['a'])
check('fixture 3', solve(['a', 'b'], ['a'], ['b'], ['b'], []), ['a', 'b'])
check('fixture 4', solve(['a'], ['a', 'missing'], [], [], []), ['a'])
check('fixture 5', solve(['a', 'b'], ['a', 'b'], [], ['b'], ['b']), ['a'])
check('fixture 6', solve(['z', 'a'], ['z', 'a', 'z'], [], [], []), ['a', 'z'])
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)

Boundary fixture	Actual	Expected	Outcome
fixture 1	`[]`	`[]`	Passed
fixture 2	`['a']`	`['a']`	Passed
fixture 3	`['a', 'b']`	`['a', 'b']`	Passed
fixture 4	`['a']`	`['a']`	Passed
fixture 5	`['a', 'b']`	`['a']`	Failed
fixture 6	`['a', 'z']`	`['a', 'z']`	Passed

SHA-256 / 7e806ebdf28ecc7c09d2a4c34d13fb180f40b2d7657a4081fef0f1d417a21956

2 / The unsuccessful fix

Exit 1

"""Failure Map reference implementation. Python standard library only."""
import json

N = 1
observations = []
def solve(available, declared, excluded, forced, forbidden):
    names = (set(declared) - set(excluded)) | set(forced)
    names &= set(available)
    names -= set(forbidden) - set(forced)
    return sorted(names)
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('fixture 1', solve([], [], [], [], []), [])
check('fixture 2', solve(['a', 'b'], ['a', 'b'], ['b'], [], []), ['a'])
check('fixture 3', solve(['a', 'b'], ['a'], ['b'], ['b'], []), ['a', 'b'])
check('fixture 4', solve(['a'], ['a', 'missing'], [], [], []), ['a'])
check('fixture 5', solve(['a', 'b'], ['a', 'b'], [], ['b'], ['b']), ['a'])
check('fixture 6', solve(['z', 'a'], ['z', 'a', 'z'], [], [], []), ['a', 'z'])
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)

Boundary fixture	Actual	Expected	Outcome
fixture 1	`[]`	`[]`	Passed
fixture 2	`['a']`	`['a']`	Passed
fixture 3	`['a', 'b']`	`['a', 'b']`	Passed
fixture 4	`['a']`	`['a']`	Passed
fixture 5	`['a', 'b']`	`['a']`	Failed
fixture 6	`['a', 'z']`	`['a', 'z']`	Passed

SHA-256 / dc35daf98d91becd60a76a6b3f1c085c2360b6066f2e313d44020cbb3e796108

HELD IN THE MEMBER ARCHIVE

The verified repair and its recorded checks are member-only.

This mechanism has 6 recorded checks per implementation. The open-access tier publishes the failure and the unsuccessful fix; the repaired source that passes every check, and the observations that prove it, are available to members.

Every case sharing this mechanism uses the same contract and the same repair, so this one record is held back for all of them.

Member access is invitation-based. Sign in with your invited account to inspect the repair.

Verification & scope

This reproducer isolates one failure mechanism. Results cover the supplied fixtures. Variants within a family share a test contract and should remain grouped when constructing evaluation splits. Related mechanisms with a shared evaluation_group must also remain together; these controlled models are not independent production incidents.

Observations recorded using Python 3.12.14 at 2026-09-29T14:38:33.899861+00:00.

Case digest / f7b05b58a320f1b4241305b7d06ebba1ad997c40c5086c9a9e1a0568d74fa39e