fix: make daily content maintenance honest and repository-aware

[ECorreia45]

Summary

• Preserve both daily cron schedules: factory triage at 09:23 UTC and maintenance at 10:11 UTC
• Replace root-npm assumptions with repository-specific checks; real failures fail the run
• Keep useful deduplicated failing-PR triage; remove automatic merging and explicitly report unsupported automatic source/dependency repair
• Restrict unattended and issue-triggered AI proposals to README.md documentation drafts, with read-only example context and no claims that code issues were implemented
• Reuse fail-closed provider/publication guards; zero-exit quota errors fail, protected files/Git state stay unchanged, and checks rerun before publishing a draft
• Do not expose provider credentials or run AI calls in pull-request validation; do not persist checkout credentials or give package checks GitHub/OpenAI token environment variables

Repository-specific validation

The development branch is a project-link catalog, with no root npm project. Validate README structure/local links and JSON/workflow syntax. External URL availability and linked project branches are not tested.

Source changes

None.

Verification

• 40 maintenance/adapter tests passed on Python 3.12
• Bash syntax and actionlint 1.7.7 passed for both workflows
• Full repository validation passed locally on Node 22.23.3 (and Node 24), including applicable regressions and the actual nested tutorial build
• No live AI/provider billing calls, merges, credential changes, or billing changes were made
• Remote CI for this exact commit must be checked separately

Limits and rollout

This draft does not activate changes on the default branch. Human review and merge are required. The existing provider credit problem remains an external blocker; this change exposes it instead of masking it as successful maintenance. Automated source repair remains explicitly unsupported until adequate test coverage exists. Draft publication guards are not an execution sandbox.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview