docs: archive stale plans and expose current development state - #199
Merged
Conversation
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_6ff9f24a-ae5b-4205-8ef7-ba932d1ba0d9) |
Keep the archive/CURRENT_WORK entry point and the L1–L4/L9 closures from #197. The gap table names the contracts and the remaining QA limits (attemptId, GPU, UI-to-render).
PR Review — Loreframe StudioRisk: low Automated review from Findings
Changed files
CONTRIBUTING checklist
Posted by the repo PR review workflow. Re-runs on each push to the PR. |
Code healthQuality score: 53.0/100Higher is better. The score is a trend dashboard; the independent ratchet below remains the CI gate.
Change vs PR base: +0.0 points.
Markdown, JSON catalogs and tests are out of this table. Only Most complex functions
Trend vs baseline
Ratchet passed. |
CURRENT_WORK now treats the manual 2D speech workshop as merged on a0bf91c. The remaining limit is artistic validation, not the RAM-safe panel tests already in that PR.
IAnMove
added a commit
that referenced
this pull request
Sep 6, 2026
IAnMove
added a commit
that referenced
this pull request
Sep 6, 2026
The archived L12 table treated shot_numbers: [2] as take 2. Mark that gap addressed in this PR and keep mobile/GPU as remaining QA limits.
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
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.
Resumen ejecutivo
Los agentes podían reabrir tareas terminadas o elegir main como base siguiendo fases y handoffs caducados. CURRENT_WORK distingue lo integrado, lo pendiente y el trabajo en curso; SLICE_QUEUE conserva solo la cola vigente.
Riesgo bajo: documentación y filtro de búsqueda del archivo; sin código, prompts, datos, servidores ni permisos de GitHub modificados. Archivar propuestas no declara que estén todas implementadas.
Validación
tests/test_labs_wizard_action_matrix.pypasan.git diff --checkpasa.origin/developmentpasa: LOC producción/tests y complejidad sin cambios. Ejecutado sobre 71c1f5d3; el amend posterior solo actualiza la mención documental de PR feat(video3d): add a real 3D stage beside the 2.5D compositor #198.Alcance local separado
Por petición del usuario también se archivaron 54 documentos locales no versionados y se redujeron cuatro guías duplicadas a una guía corta con referencias. Esa limpieza y ESTADO_LOCAL.md permanecen fuera de Git; no se incluyen rutas privadas, conversaciones, pesos ni medios en este PR.
Base inspeccionada: development ebed43f. No merge automático; no release a main.
Note
Low Risk
Documentation and archive search filtering only; no application code, runtime behavior, or GitHub permissions change. Main operational risk is agents briefly missing the new entry point if they skip updated CONTRIBUTING links.
Overview
Redirects contributors and agents away from outdated F1–F12 phase packets and long slice-queue history so they stop reopening merged work or treating
mainas the integration base.New entry point:
docs/development/CURRENT_WORK.mdrecords what is integrated ondevelopment, what is in flight, and verified pending refactors/QA. CONTRIBUTING and BRANCHING now tell readers to start there (and the slim SLICE_QUEUE) instead of the old execution baseline.Archive: The September architecture wave (
EXECUTION_BASELINE, full SLICE_QUEUE,fase1–fase12) moves underdocs/archive/2026-09-06/with a short archive README.docs/archive/.ignorekeeps ordinary ripgrep from surfacing that tree unless searched explicitly. Active EXECUTION_BASELINE and SLICE_QUEUE are replaced by short stubs that point at CURRENT_WORK and the archive.Labs matrix: LABS_WIZARD_ACTION_MATRIX is reframed as a detailed L0 reference (not the startup checklist), marks several gap IDs as addressed in #183, and narrows remaining QA (e.g. specific
attemptId, mobile, bounded audiovisual) without changing fixtures.Reviewed by Cursor Bugbot for commit 554c356. Configure here.