Conversation
…rver-free Census family lifecycle-transition-forbidden (2 cases, both @fusion/core): the two cases asserted automatic backward moves the F2 rank rules forbid. live-move-path-undeclared-target: archived -> todo is refused even with recoveryRehome, which is an adjacency bypass and never a containment bypass. The capability half moves to resolveContainedBackwardTargetForTask, so the stranded-card reach the case was written to protect is still pinned. renamed-board-reopen: the engine-sourced checking -> queued bounce is refused and the card holds, which is what prevents the stale-passed-result hazard rather than the reopen clear. The clear keeps its own user-sourced case. New server-free policy test owns the invariant: F1-F5, the moveSource carve-out, the reason partition, and every role-fixed reason authorizing no role change. Verified by four mutations (F2 relaxed, scoping removed, F5 deleted, a recovery reason widened) - each fails naming the rule and pair. No guard file changed. Co-authored-by: Fusion <noreply@runfusion.ai> Fusion-Task-Id: FUSI-036
ThreatCrush Security Scan4589 finding(s) HIGH/CRITICAL: 43 | MEDIUM: 4035 | LOW: 511
…and 4539 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated PR for FUSI-036.
REGRESSION follow-up (FUSI-020 Step 5, family 7 of 7):
lifecycle-transition-forbidden- 2 cases across 2 engine test files assert a lifecycle move that the FN-217 F2 rank rules now forbid. This is a policy-guard regression, not stale text: the test is asking the engine to perform a move the lifecycle containment contract deliberately blocks (e.g. an automatic path attempting a backward move out of a review lane or into intake). Fixing it by relaxing the guard is exactly the barred appeasement - the guard is correct and the test's expectation violates it. Read FN-207/FN-217 and the lifecycle containment rules in AGENTS.md, then rewrite the case to assert the correct contained behavior (the move is refused and the card holds or routes per the current lifecycle role). First red run: main push Runfusion#3158 (b37d0fe). Census: docs/solutions/test-failures/main-full-suite-census-2026-09-25.md (familylifecycle-transition-forbidden). Relevant files include src/tests/in-review-unmet-dependency-reconcile.test.ts and src/tests/workflow-node-execution-needs.test.ts. Reproduce: pnpm --filter @fusion/engine exec vitest run --silent=passed-only --reporter=dot. Per FN-5893 assert the containment invariant across every surface that attempts a forbidden move, not just these two files.