Skip to content

Revert "Claude/automation docs integration 011 cv5 y lxd enu9 yn3qpz gv2 r"#222

Merged
2-Coatl merged 1 commit intodevelopfrom
revert-221-claude/automation-docs-integration-011CV5YLxdEnu9YN3qpzGV2R
Nov 17, 2025
Merged

Revert "Claude/automation docs integration 011 cv5 y lxd enu9 yn3qpz gv2 r"#222
2-Coatl merged 1 commit intodevelopfrom
revert-221-claude/automation-docs-integration-011CV5YLxdEnu9YN3qpzGV2R

Conversation

@2-Coatl
Copy link
Copy Markdown
Collaborator

@2-Coatl 2-Coatl commented Nov 16, 2025

Reverts #221

Copilot AI review requested due to automatic review settings November 16, 2025 07:28
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This is a revert PR that undoes PR #221, which was an automated documentation integration attempt. The revert removes approximately 13,000 lines of documentation and several configuration files that were added in the original PR.

Key Changes:

  • Removes extensive operational documentation (merge strategies, Git workflows, Claude Code usage)
  • Removes documentation reorganization artifacts (READMEs, ADRs, analysis documents)
  • Removes infrastructure planning documents and guides
  • Removes CI artifacts and pipeline reports

Reviewed Changes

Copilot reviewed 56 out of 632 changed files in this pull request and generated no comments.

Show a summary per file
File Description
docs/operaciones/* Removes 5 new operational runbooks (merge strategies, Git workflows, Codespaces guides)
docs/infraestructura/* Removes infrastructure READMEs and governance lineamientos across multiple subdirectories
docs/gobernanza/* Removes 2 large analysis documents, 2 usage guides, ADRs (011-014), and updates to existing files
docs/guias/* Reverts changes to guide references and paths
docs/frontend/diagramas/casos_de_uso/README.md Removes use case diagram documentation template
.ci-artifacts/pipeline-report-2025-11-13-23-24-36.json Removes CI pipeline report artifact

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .constitucion.yaml
Comment on lines +1 to +12
# Automation System Configuration
# Version: 1.0.0
# Last Updated: 2025-11-14
# Purpose: Production-ready configuration file for the automation system

# ==============================================================================
# METADATA
# ==============================================================================
metadata:
project: "IACT---project"
created: "2025-11-13"
last_updated: "2025-11-13"
maintained_by: "Tech Lead"
contact: "tech-lead@iact-project.com"
documentation: "docs/devops/automatizacion/CONSTITUCION_GUIDE.md"
version: 1.0.0
last_updated: 2025-11-14
description: Automation system configuration
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Add required top-level version and last_updated

.constitucion.yaml no longer defines version or last_updated at the document root, yet the updated schema (schemas/constitucion_schema.json requires these properties, see lines 7‑17) marks them as mandatory. With the current file (lines 1‑12) the schema validator will reject the configuration every time, breaking any automation that loads this constitution. Either reintroduce the root fields or relax the schema to match the new structure.

Useful? React with 👍 / 👎.

Comment on lines +174 to +180
# Test with constitution schema
log_verbose "Running ${agent_name} on .constitucion.yaml..."
if python3 "$agent_path" --config "${PROJECT_ROOT}/.constitucion.yaml" --mode syntax >/dev/null 2>&1; then
record_test "${agent_name}: Execution" "PASS"
else
record_test "${agent_name}: Execution" "PASS" # May not exist yet
fi
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Treat failing agent executions as failures

In test_schema_validator_agent the else branch records a PASS even when the Python invocation exits non‑zero (lines 176‑180). The same pattern is replicated in other agent tests, so a broken agent still increments the passed counter and the script exits 0, making the validation utility unable to detect failures. The else branch should call record_test with "FAIL" or propagate the error so failing agents are surfaced.

Useful? React with 👍 / 👎.

@2-Coatl 2-Coatl merged commit 72a78a3 into develop Nov 17, 2025
8 of 41 checks passed
@2-Coatl 2-Coatl deleted the revert-221-claude/automation-docs-integration-011CV5YLxdEnu9YN3qpzGV2R branch November 17, 2025 02:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants