Expose the original calculation history for validation, joint obligations, at-risk placement, and ordered preferences. The advanced trace view groups the actual run by phase, atomic planning decision, and candidate evaluation, including joint multi-date branches, shared placements, pruning reasons, and earned-entitlement activation. The history is captured during the producing run rather than reconstructed afterward.
Acceptance criteria
The calculation context exposes trace readiness separately from the planning outcome.
The outcome can become available before trace delivery completes.
Trace events for validation, obligations, at-risk balances, and every ordered preference come from the original run.
Events are grouped as calculation phase, atomic planning decision, then actual candidate evaluations.
A joint obligation branch remains one atomic multi-date decision rather than artificial independent day steps.
Shared placements and earned-entitlement activation appear in their real order.
Accepted, rejected, pruned, not-examined, and ineligible branches retain their real reason; no unperformed comparison receives a vector.
One initial state plus ordered deltas can reconstruct the planner state through the traced phases.
The advanced annual-calendar view can navigate the traced phases and expand candidate evaluations.
Only the latest run’s trace is retained in memory and a new calculation discards the previous one.
Tests use the public planner and rendered annual-calendar seams and include joint obligations, at-risk placement, ordered preferences, shared placements, and an earned-entitlement chain.
Blocked by
#47 — Afficher l’explication stable d’un placement final
## Parent
#46
## What to build
Expose the original calculation history for validation, joint obligations, at-risk placement, and ordered preferences. The advanced trace view groups the actual run by phase, atomic planning decision, and candidate evaluation, including joint multi-date branches, shared placements, pruning reasons, and earned-entitlement activation. The history is captured during the producing run rather than reconstructed afterward.
## Acceptance criteria
- [ ] The calculation context exposes trace readiness separately from the planning outcome.
- [ ] The outcome can become available before trace delivery completes.
- [ ] Trace events for validation, obligations, at-risk balances, and every ordered preference come from the original run.
- [ ] Events are grouped as calculation phase, atomic planning decision, then actual candidate evaluations.
- [ ] A joint obligation branch remains one atomic multi-date decision rather than artificial independent day steps.
- [ ] Shared placements and earned-entitlement activation appear in their real order.
- [ ] Accepted, rejected, pruned, not-examined, and ineligible branches retain their real reason; no unperformed comparison receives a vector.
- [ ] One initial state plus ordered deltas can reconstruct the planner state through the traced phases.
- [ ] The advanced annual-calendar view can navigate the traced phases and expand candidate evaluations.
- [ ] Trace capture cannot change candidate order, completed phases, incumbent, or outcome.
- [ ] Only the latest run’s trace is retained in memory and a new calculation discards the previous one.
- [ ] Tests use the public planner and rendered annual-calendar seams and include joint obligations, at-risk placement, ordered preferences, shared placements, and an earned-entitlement chain.
## Blocked by
- #47 — Afficher l’explication stable d’un placement final
Original-run early-phase tracing, separate artifact readiness and snapshot ownership exist. However, the published preference trace test explicitly expects the used first-compatible balance candidate to remain evaluated-rejected, with a separate chosen placement event. Candidate acceptance and decision grouping need verification against the exact-history requirement; local commit 51978f7 changes TraceRecorder candidate grouping. The required joint-obligation/shared/earned-chain trace coverage also needs verification before closure.
Evidence: reviewed issue requirements/discussions and f1f0835 (published application source; live main 57a39c81 only adds Renovate configuration). Tested an isolated checkout of the published source: 20 test files, 157/157 tests passed, including the five benchmark scenarios. Local commit 51978f7 and uncommitted edits were inspected separately and are not evidence of published completion.
Completion audit — 2026-10-02
Original-run early-phase tracing, separate artifact readiness and snapshot ownership exist. However, the published preference trace test explicitly expects the used first-compatible balance candidate to remain evaluated-rejected, with a separate chosen placement event. Candidate acceptance and decision grouping need verification against the exact-history requirement; local commit 51978f7 changes TraceRecorder candidate grouping. The required joint-obligation/shared/earned-chain trace coverage also needs verification before closure.
Evidence: reviewed issue requirements/discussions and f1f0835 (published application source; live main 57a39c81 only adds Renovate configuration). Tested an isolated checkout of the published source: 20 test files, 157/157 tests passed, including the five benchmark scenarios. Local commit 51978f7 and uncommitted edits were inspected separately and are not evidence of published completion.
Implemented with $luna-verified-implement and independently verified.
The original run records obligation branches, sequential at-risk placement, preference comparisons, shared satisfaction, earned activation, and exact state deltas with selected branch ancestry.
Validation: 198/198 tests across 23 files, app/spec TypeScript checks, ESLint, and production build pass. Chromium keyboard, focus-restoration, background comparison, and responsive checks at 375/768/1440 pixels pass with no page errors. Original benchmark outcomes match the pre-change baseline in all five scenarios, with and without tracing.
The implementation is in the local working tree based on 0ce33cc9d6fe7381965a9162571abe205d0b7350; no commit or push has been made.
Implemented with $luna-verified-implement and independently verified.
The original run records obligation branches, sequential at-risk placement, preference comparisons, shared satisfaction, earned activation, and exact state deltas with selected branch ancestry.
Validation: 198/198 tests across 23 files, app/spec TypeScript checks, ESLint, and production build pass. Chromium keyboard, focus-restoration, background comparison, and responsive checks at 375/768/1440 pixels pass with no page errors. Original benchmark outcomes match the pre-change baseline in all five scenarios, with and without tracing.
The implementation is in the local working tree based on 0ce33cc9d6fe7381965a9162571abe205d0b7350; no commit or push has been made.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Parent
#46
What to build
Expose the original calculation history for validation, joint obligations, at-risk placement, and ordered preferences. The advanced trace view groups the actual run by phase, atomic planning decision, and candidate evaluation, including joint multi-date branches, shared placements, pruning reasons, and earned-entitlement activation. The history is captured during the producing run rather than reconstructed afterward.
Acceptance criteria
Blocked by
mentioned in issue #50
mentioned in issue #53
Completion audit — 2026-10-02
Original-run early-phase tracing, separate artifact readiness and snapshot ownership exist. However, the published preference trace test explicitly expects the used first-compatible balance candidate to remain evaluated-rejected, with a separate chosen placement event. Candidate acceptance and decision grouping need verification against the exact-history requirement; local commit 51978f7 changes TraceRecorder candidate grouping. The required joint-obligation/shared/earned-chain trace coverage also needs verification before closure.
Evidence: reviewed issue requirements/discussions and
f1f0835(published application source; live main57a39c81only adds Renovate configuration). Tested an isolated checkout of the published source: 20 test files, 157/157 tests passed, including the five benchmark scenarios. Local commit 51978f7 and uncommitted edits were inspected separately and are not evidence of published completion.Implemented with $luna-verified-implement and independently verified.
The original run records obligation branches, sequential at-risk placement, preference comparisons, shared satisfaction, earned activation, and exact state deltas with selected branch ancestry.
Validation: 198/198 tests across 23 files, app/spec TypeScript checks, ESLint, and production build pass. Chromium keyboard, focus-restoration, background comparison, and responsive checks at 375/768/1440 pixels pass with no page errors. Original benchmark outcomes match the pre-change baseline in all five scenarios, with and without tracing.
The implementation is in the local working tree based on 0ce33cc9d6fe7381965a9162571abe205d0b7350; no commit or push has been made.
mentioned in issue #46
Preserved GitLab #49 history: source attribution, exact timestamps, discussion grouping and review positions. Historical diff snapshots: 0; visible source notes: 5.
gitlab-35-issue-49.md (SHA-256
40631ad60694fac4d6441379e2e52da1c045fd05d99d057c5fc86634da673fed)gitlab-35-issue-49.json (SHA-256
befd60c4a42bb58d696a08dbaaff9849a87852e7de6da4d33cf79930662960a0)Old CI job execution and reports are omitted. Original source files and rollback backups remain protected.