finalproject-JCM - #281
Conversation
Entrega Final — Juan Andrés Chacón Matteo Proyecto: Components DB
📝 WalkthroughWalkthroughSe reemplazan plantillas en ChangesDocumentación del proyecto
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
🧹 Nitpick comments (1)
readme.md (1)
236-237: 🩺 Stability & Availability | 🔵 TrivialBound the blocking Gemini request.
Because this endpoint is explicitly documented as blocking, specify finite upstream timeouts, upload/page limits, and the controlled failure response. Otherwise Gemini latency or failure can tie up request workers.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@readme.md` around lines 236 - 237, Update the documentation describing the blocking Gemini call and HTML response to specify finite upstream timeouts, PDF upload/page limits, and the controlled response returned when Gemini times out or fails. Ensure the documented limits and failure behavior clearly prevent the endpoint from waiting indefinitely.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@readme.md`:
- Line 44: Update the README extraction-pipeline descriptions to document both
PyMuPDF text extraction and Gemini-based OCR for scanned or image-based PDF
content, matching the mixed extraction behavior specified in prompts.md. Apply
the same architecture clarification to the additional occurrence referenced by
the review.
- Line 320: Update the US-02 performance statement in the README to either
document the benchmark environment, dataset size, query, and measurement method
supporting the “~2 ms” figure, or remove the exact figure while retaining only a
qualified performance description.
- Line 149: Update the integration-test description in readme.md to reference
the production extraction route
/htmx/ai/extract-parameters/<uuid:component_type_id>/ instead of POST
/ai/extract/. Apply the same route correction to the related content at the
additionally referenced section, preserving the documented HTMX, Google API
mock, JSON parsing, and OOB-tag behavior.
- Around line 239-241: Update the “Endpoint de Filtros Dinámicos” response
documentation to describe text parameters as rendered text inputs and specify
their matching semantics. Keep the existing numeric and boolean control
descriptions unchanged, and ensure all supported ComponentTypeParameter data
types are covered.
- Around line 59-65: The README setup instructions reference unavailable
dependency, runtime, and infrastructure configuration. Update the setup sections
in readme.md to describe only the currently supported minimal setup, removing or
qualifying Python, requirements, Django, and PostgreSQL version claims that
cannot be verified from the repository; do not retain commands for missing
manifests or configuration files.
- Line 142: Actualiza la sección “Protección CSRF y XSS” del README: indica que
HTMX solo envía el token CSRF en peticiones asíncronas cuando se configura
explícitamente mediante hx-headers o htmx:configRequest, y reformula la
afirmación sobre XSS para describir el autoescape predeterminado de Django junto
con sus límites en contenido safe, atributos sin comillas y contenido style
escapado.
- Line 308: Update the documented HTMX fallback flow so HTTP 422 responses are
explicitly handled and their alert content is rendered, using HTMX
response-target configuration or an htmx:responseError event handler; ensure the
existing retry-failure behavior remains a controlled 422 response.
---
Nitpick comments:
In `@readme.md`:
- Around line 236-237: Update the documentation describing the blocking Gemini
call and HTML response to specify finite upstream timeouts, PDF upload/page
limits, and the controlled response returned when Gemini times out or fails.
Ensure the documented limits and failure behavior clearly prevent the endpoint
from waiting indefinitely.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| 3. **Árboles Documentales (Document Trees):** Organización jerárquica ilimitada de documentación técnica utilizando el patrón Materialized Path (`django-treebeard`). | ||
| 4. **Gestión de Documentos y Etiquetas transversales:** Subida de documentos con control de versiones (una subida nueva no pisa la anterior, la versiona) y un sistema de clasificación por tags. | ||
| 5. **Búsqueda Paramétrica Avanzada:** Filtros dinámicos generados en función del tipo de componente que permiten búsquedas precisas (ej. Ur >= 24kV) sin penalizar el rendimiento. | ||
| 6. **Extracción de Parámetros con Inteligencia Artificial:** Integración de un pipeline que recibe un datasheet en PDF, extrae el texto (PyMuPDF) y usa un LLM (Google Gemini) para extraer automáticamente los valores técnicos con una UI de validación humana (split-screen). |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Document the OCR portion of the extraction pipeline.
prompts.md lines 15-17 require mixed text extraction plus OCR with Gemini, but these README descriptions only document PyMuPDF text extraction. Reconcile both documents so the final architecture reflects the implemented behavior rather than an incomplete pipeline.
Also applies to: 112-112
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@readme.md` at line 44, Update the README extraction-pipeline descriptions to
document both PyMuPDF text extraction and Gemini-based OCR for scanned or
image-based PDF content, matching the mixed extraction behavior specified in
prompts.md. Apply the same architecture clarification to the additional
occurrence referenced by the review.
| # 2. Crear y activar el entorno virtual (Python 3.14+) | ||
| python -m venv .venv | ||
| source .venv/bin/activate # Linux/Mac | ||
| # .venv\Scripts\activate # Windows | ||
|
|
||
| ### **2.2. Descripción de componentes principales:** | ||
| # 3. Instalar las dependencias de desarrollo | ||
| pip install -r requirements/development.txt |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
fd -a 'pyproject.toml|requirements|Dockerfile|docker-compose|.python-version|.tool-versions'
rg -n 'requires-python|Django|django|postgres|python' pyproject.toml requirements Dockerfile docker .python-version .tool-versions 2>/dev/nullRepository: LIDR-academy/AI4Devs-finalproject
Length of output: 171
🏁 Script executed:
#!/bin/bash
set -u
echo "== repo files (top-level candidates) =="
git ls-files | sed -n '1,220p'
echo
echo "== readme relevant =="
if [ -f readme.md ]; then
nl -ba readme.md | sed -n '45,125p'
fi
if [ -f README.md ]; then
nl -ba README.md | sed -n '45,125p'
fi
echo
echo "== manifest/dev files =="
git ls-files | rg -i '(^|/)(pyproject\.toml|requirements.*\.txt|poetry\.lock|pipfile(\.lock)?|setup\.cfg|setup\.py|mako|Dockerfile|docker-compose.*|compose.*|\.python-version|\.tool-versions)$' || true
echo
echo "== search relevant terms =="
rg -n --hidden --glob '!*.log' --glob '!coverage/**' --glob '!dist/**' --glob '!build/**' 'requires-python|Python 3\.14|django|Django|postgres|postgres.*16|16|python_requires|python_version|python-version' . || trueRepository: LIDR-academy/AI4Devs-finalproject
Length of output: 3881
Align the README setup steps with this repository’s checked-in toolchain.
readme.md references Python 3.14+, requirements/development.txt, Django 6.0, and PostgreSQL 16, but the checked-in repo only contains prompts.md and readme.md — no manifests, Docker config, or version constraints. Add the actual files/config to match these instructions, or update the README to describe the intended minimal setup.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@readme.md` around lines 59 - 65, The README setup instructions reference
unavailable dependency, runtime, and infrastructure configuration. Update the
setup sections in readme.md to describe only the currently supported minimal
setup, removing or qualifying Python, requirements, Django, and PostgreSQL
version claims that cannot be verified from the repository; do not retain
commands for missing manifests or configuration files.
| - El despliegue de base de datos se maneja a través de volúmenes persistentes en Docker y copias de seguridad programadas de PostgreSQL. | ||
|
|
||
| ### 2.5. Seguridad | ||
| - **Protección CSRF y XSS:** Al usar Django Templates y HTMX, el token CSRF va incluido en el encabezado de todas las peticiones asíncronas automáticamente. Django sanitiza por defecto las salidas HTML previniendo inyecciones XSS. |
There was a problem hiding this comment.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "## repository files matching readme.md"
git ls-files | grep -iE '(^|/)readme\.md$' || true
echo
echo "## relevant markdown line"
if [ -f readme.md ]; then
nl -ba readme.md | sed -n '130,152p'
fi
echo
echo "## htmx/django csrf references"
rg -n --no-heading -i 'hx-headers|csrf|htmx|HTMX|CSRF|XSS|sanitiz|escape' -S . \
-g '!venv/**' -g '!node_modules/**' -g '!dist/**' -g '!build/**' | head -200
echo
echo "## locate templates/static"
git ls-files | grep -E '(templates|static|\.html|\.md|\.py|requirements\.txt|pyproject\.toml)$' | sed -n '1,200p'Repository: LIDR-academy/AI4Devs-finalproject
Length of output: 288
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "## relevant markdown line"
sed -n '130,152p' readme.md | awk '{printf "%4d\t%s\n", NR+129, $0}'
echo
echo "## htmx/django csrf references"
grep -RIn -Ei 'hx-headers|csrf|htmx|HTMX|XSS|sanitiz|escape' . \
--exclude-dir=venv --exclude-dir=node_modules --exclude-dir=dist --exclude-dir=build \
| head -200
echo
echo "## config files"
git ls-files | grep -E '(^|/)(templates|requirements\.txt|pyproject\.toml|settings\.py|urls\.py|views\.py)$|\.html$' | sed -n '1,200p'Repository: LIDR-academy/AI4Devs-finalproject
Length of output: 6238
🌐 Web query:
HTMX CSRF integration hx-headers documentation
💡 Result:
To integrate CSRF protection with htmx using headers, you can use either the hx-headers attribute or the htmx:configRequest event. ### 1. Using hx-headers The hx-headers attribute allows you to add custom headers to requests [1][2]. It is inherited, meaning you can place it on a parent element (like or ) to apply the CSRF token to all htmx requests within that subtree [2][3]. * Basic JSON syntax: * Dynamic values: You can use the js: or javascript: prefix to evaluate values dynamically (e.g., calling a function that retrieves the current token) [1][2]. Note: Using the javascript: prefix introduces security considerations related to XSS if the generated values include user input [1][2]. ### 2. Using htmx:configRequest The htmx:configRequest event is often considered a more robust and secure approach for dynamic security headers, as it avoids inline JavaScript in attributes [4][5]. You can listen for this event on document.body to intercept and modify request headers globally [5][3][6]. Example: document.body.addEventListener('htmx:configRequest', (event) => { event.detail.headers['X-CSRFToken'] = '{{ csrf_token }}'; }); This method works well for framework-specific tokens (like those in Django or Rails) where you can inject the token variable directly into your template [7][3][6]. For further implementation details, see the official htmx documentation on hx-headers and the htmx:configRequest event.
Citations:
- 1: https://htmx.org/attributes/hx-headers/
- 2: https://four.htmx.org/reference/attributes/hx-headers
- 3: Passing a CSRF token in the request header bigskysoftware/htmx#70
- 4: Dynamic csrf prevention bigskysoftware/htmx#3187
- 5: https://four.htmx.org/reference/events/htmx-config-request
- 6: Add csrf token to ajax header bigskysoftware/htmx#276
- 7: https://django-htmx.readthedocs.io/en/latest/tips.html
🌐 Web query:
Django template escaping autoescaping XSS contexts safe filter documentation
💡 Result:
Django’s template system provides automatic HTML escaping by default to protect against Cross-Site Scripting (XSS) attacks [1][2][3]. This mechanism ensures that potentially harmful characters—specifically <, >, ', ", and &—are converted into their safe HTML entity equivalents when rendering variables [1][2][3]. Key Concepts: Automatic Escaping: When auto-escaping is enabled (the default state), Django automatically applies HTML escaping to the output of every variable tag [1][2][3]. This process occurs after all template filters have been applied to the variable [4][5]. String literals in templates are not automatically escaped, as they are considered under the direct control of the template author [3]. Safe Filter: The safe filter is used to mark a string as "safe" from further HTML escaping [4][5][6]. When a variable is marked as safe, Django will not escape its contents, even if auto-escaping is active [4][5]. This is typically used for content that is known to be trusted and properly sanitized, such as HTML generated by a trusted library [7][4]. Managing Auto-Escaping: - Autoescape Tag: You can explicitly control auto-escaping for blocks of code using the {% autoescape on/off %}... {% endautoescape %} template tag [1][4][3]. - Escape Filter: The escape filter can be used to manually escape a variable [1]. When used in an environment where auto-escaping is already active, the escape filter is "smart" and will not double-escape data [1][4][3]. - Force_escape Filter: Use the force_escape filter if you specifically require multiple rounds of escaping [4][5][6]. - Escapeseq Filter: When dealing with sequences (e.g., lists), use the escapeseq filter to ensure every individual element is properly escaped [4][5][6]. Security Considerations: While Django's auto-escaping protects against most XSS, it is not a universal solution [7]. It does not protect against vulnerabilities arising from unsafe usage in certain HTML contexts, such as injecting untrusted data into attributes like onmouseover or inside style tags without proper quoting [7]. Always remain cautious when using the safe filter, mark_safe, or disabling auto-escaping [7]. Top Results: [1] https://docs.djangoproject.com/en/5.2/ref/templates/language/ [7] https://docs.djangoproject.com/en/5.2/topics/security/ [4] https://docs.djangoproject.com/en/6.0/ref/templates/builtins/ [3] https://docs.djangoproject.com/en/dev/ref/templates/language/
Citations:
- 1: https://docs.djangoproject.com/en/5.2/ref/templates/language/
- 2: https://docs.djangoproject.com/en/6.1/ref/templates/language/
- 3: https://docs.djangoproject.com/en/dev/ref/templates/language/
- 4: https://docs.djangoproject.com/en/6.0/ref/templates/builtins/
- 5: https://docs.djangoproject.com/en/5.1/ref/templates/builtins/
- 6: https://django.readthedocs.io/en/stable/ref/templates/builtins.html
- 7: https://docs.djangoproject.com/en/5.2/topics/security/
Correct the CSRF/XSS security claim in the README.
HTMX does not automatically include Django CSRF tokens in AJAX requests unless hx-headers or htmx:configRequest is configured. Also rephrase the XSS claim to reflect Django’s default autoescaping while noting it does not cover unsafe contexts such as unescaped safe content, unquoted attribute interpolation, or escaped style content.
🧰 Tools
🪛 LanguageTool
[style] ~142-~142: Es preferible evitar este anglicismo.
Context: ...ones asíncronas automáticamente. Django sanitiza por defecto las salidas HTML previniend...
(SANITIZAR)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@readme.md` at line 142, Actualiza la sección “Protección CSRF y XSS” del
README: indica que HTMX solo envía el token CSRF en peticiones asíncronas cuando
se configura explícitamente mediante hx-headers o htmx:configRequest, y
reformula la afirmación sobre XSS para describir el autoescape predeterminado de
Django junto con sus límites en contenido safe, atributos sin comillas y
contenido style escapado.
Source: MCP tools
| ### 2.6. Tests | ||
| Se utiliza `pytest`, `pytest-django` y `factory-boy`. | ||
| - **Unit Tests:** Validación de los managers personalizados y funciones de formateo (ej. limpiadores de strings JSON de Gemini). | ||
| - **Integration Tests:** Verifican los flujos HTMX; por ejemplo, que al enviar el formulario `POST /ai/extract/` el sistema realmente haga un mock a la API de Google, parsee el JSON y retorne un template HTML parcial con los tags OOB (`hx-swap-oob`) correctos para actualizar la vista sin errores. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Align the documented extraction route.
The test plan refers to POST /ai/extract/, while the API specification defines /htmx/ai/extract-parameters/<uuid:component_type_id>/. This mismatch can leave tests covering a nonexistent route instead of the production endpoint.
Also applies to: 234-237
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@readme.md` at line 149, Update the integration-test description in readme.md
to reference the production extraction route
/htmx/ai/extract-parameters/<uuid:component_type_id>/ instead of POST
/ai/extract/. Apply the same route correction to the related content at the
additionally referenced section, preserving the documented HTMX, Google API
mock, JSON parsing, and OOB-tag behavior.
| **2. Endpoint de Filtros Dinámicos (Búsqueda Paramétrica)** | ||
| - **Ruta:** `GET /htmx/components/filters/<uuid:component_type_id>/` | ||
| - **Respuesta (HTML):** Retorna un formulario HTML que itera sobre los `ComponentTypeParameter` del tipo elegido, renderizando inputs `<input type="number">` o `<select>` dependiendo de si el tipo de dato subyacente del parámetro es numérico o booleano. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Specify filtering for text parameters.
The data model supports numeric, text, and boolean parameters, but this endpoint only defines numeric and boolean controls. Document the text input and its matching semantics so the search contract covers every supported parameter type.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@readme.md` around lines 239 - 241, Update the “Endpoint de Filtros Dinámicos”
response documentation to describe text parameters as rendered text inputs and
specify their matching semantics. Keep the existing numeric and boolean control
descriptions unchanged, and ensure all supported ComponentTypeParameter data
types are covered.
| 2. Instanciar `PyMuPDF` y volcar el texto del PDF subido. | ||
| 3. Crear un System Prompt fuerte que exija el esquema estricto (pasando la lista de parámetros esperados). | ||
| 4. Crear un sanitizador (regex o string manipulation) que limpie el inicio/fin de la respuesta del LLM antes de deserializar a dict. | ||
| - **Buenas Prácticas:** Proveer de mecanismos Fallback. Si el parseo falla 2 veces consecutivas (retry), devolver un error controlado al frontend mediante un HTTP 422 para que HTMX pinte un Alert. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== repo files =="
git ls-files | sed -n '1,120p'
echo "== readme around mentioned line =="
if [ -f readme.md ]; then
wc -l readme.md
sed -n '288,322p' readme.md
fi
echo "== htmx usage/config references =="
rg -n "htmx|HTTP 422|422|responseError|hx-event|event:" -S . --glob '!node_modules' --glob '!dist' --glob '!build' | sed -n '1,200p'
echo "== diff stat if available =="
git diff --stat || trueRepository: LIDR-academy/AI4Devs-finalproject
Length of output: 4187
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== repo files =="
git ls-files | sed -n '1,120p'
echo "== readme around mentioned line =="
if [ -f readme.md ]; then
wc -l readme.md
sed -n '288,322p' readme.md
fi
echo "== htmx usage/config references =="
rg -n "htmx|HTTP 422|422|responseError|hx-event|event:" -S . --glob '!node_modules' --glob '!dist' --glob '!build' | sed -n '1,200p'
echo "== diff stat if available =="
git diff -- stat || trueRepository: LIDR-academy/AI4Devs-finalproject
Length of output: 4187
🌐 Web query:
htmx docs 4xx response error responseError response handling documentation
💡 Result:
By default, htmx does not swap content for 4xx and 5xx HTTP response codes [1][2]. This behavior is a design choice to prevent error messages (which may contain arbitrary content) from disrupting the page layout [2]. To handle error responses, you have several options: 1. Configure global response handling You can modify how htmx handles specific status codes globally via the htmx.config.responseHandling configuration [1][3]. This allows you to force htmx to swap responses even for error codes: { "responseHandling": [ {"code":"422", "swap": true}, {"code":"..", "swap": false, "error":true}, {"code":"...", "swap": false} ] } 2. Use the Response Targets Extension The htmx response-targets extension is the most common way to handle errors locally [4]. It allows you to target different elements based on the status code:
Using hx-target-error handles both 4xx and 5xx responses [4]. 3. Use the hx-status attribute In newer versions of htmx (e.g., htmx 2.0+), the hx-status attribute provides granular control over swap behavior, targets, and other properties for specific status codes or ranges: 4. Handle via events You can listen for the htmx:response:error event to execute custom JavaScript when an error occurs [5][6]. This event triggers after an error status code is received but before the swap phase [5]. Note that in htmx 2.0, the event detail structure was updated to access the response via evt.detail.ctx.response [5]. Additionally, you can use the htmx:beforeSwap event to programmatically decide whether to swap an error response by setting e.detail.shouldSwap to true and e.detail.isError to false [2].Citations:
- 1: https://htmx.org/quirks/
- 2: Handling request errors bigskysoftware/htmx#3574
- 3: https://htmx.org/reference/
- 4: https://htmx.org/extensions/response-targets/
- 5: https://four.htmx.org/reference/events/htmx-response-error
- 6: https://four.htmx.org/reference
Configure HTMX error response handling for the 422 fallback.
HTMX treats 4xx responses as errors and does not swap them by default, so returning HTTP 422 alone will not render the alert. Add 422 response handling or use an event-based handler such as htmx:responseError/response-targets.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@readme.md` at line 308, Update the documented HTMX fallback flow so HTTP 422
responses are explicitly handled and their alert content is rendered, using HTMX
response-target configuration or an htmx:responseError event handler; ensure the
existing retry-failure behavior remains a controlled 422 response.
Source: MCP tools
| **Pull Request 3** | ||
| **Pull Request 2: Motor de Árboles con django-treebeard (PR #19)** | ||
| - **Descripción:** Se introdujo la dependencia externa de treebeard para Materialized Paths. Se implementaron los endpoints HTMX para las operaciones CRUD del nodo y la validación que impide el borrado accidental de ramas que contengan documentos. | ||
| - **Impacto:** Resolvió la US-02 con una solución performante a nivel de base de datos para lectura (las lecturas de sub-ramas completas ahora toman ~2ms). |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Qualify the “~2 ms” performance claim.
Add the benchmark environment, dataset size, query, and measurement method, or remove the exact figure. As written, the number is not reproducible or independently verifiable.
🧰 Tools
🪛 LanguageTool
[style] ~320-~320: En sentido figurado es preferible usar otras expresiones.
Context: ...ó la US-02 con una solución performante a nivel de base de datos para lectura (las lectura...
(A_NIVEL_DE)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@readme.md` at line 320, Update the US-02 performance statement in the README
to either document the benchmark environment, dataset size, query, and
measurement method supporting the “~2 ms” figure, or remove the exact figure
while retaining only a qualified performance description.
1 participant
Resumen
Entrega final del proyecto Components DB.
El proyecto implementa un catálogo técnico estructurado como fuente única de verdad (Single Source of Truth), que integra:
Evidencia final
Como el repositorio de código del proyecto es privado (jnchacon/components-db), se ha habilitado el acceso a la TA. Adicionalmente, se incluye como evidencia principal un recorrido funcional completo en video:
readme.mdprompts.mdResultado validado
El sistema se ha validado localmente asegurando:
Comentario final
Components DB pasó de ser una conceptualización para reemplazar archivos fragmentados (Excel y PDFs) a ser una aplicación Full-Stack moderna. Durante la recta final de su desarrollo, el ciclo completo estuvo guiado y restringido a través del meta-workflow interno LIDR Specboot, priorizando el diseño arquitectónico, el control de la deuda técnica y una interacción basada en validaciones visuales sobre meras inyecciones de código.