155e5dd5865be658bef6dfd6b0901eda119cbd5f
1913 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
155e5dd586 |
fix(tests): correct indentation in actor_loading.feature
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (pull_request) Failing after 19s
CI / push-validation (pull_request) Successful in 20s
CI / helm (pull_request) Successful in 32s
CI / quality (pull_request) Successful in 33s
CI / typecheck (pull_request) Successful in 53s
CI / security (pull_request) Successful in 1m4s
CI / coverage (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Has been skipped
CI / build (pull_request) Successful in 3m18s
CI / e2e_tests (pull_request) Successful in 6m18s
CI / integration_tests (pull_request) Successful in 7m2s
CI / unit_tests (pull_request) Successful in 8m53s
CI / docker (pull_request) Has been skipped
CI / status-check (pull_request) Failing after 1s
Fixed Gherkin syntax error where the 'LLM actor without tools' scenario had incorrect indentation (3 spaces instead of 2), which prevented the feature file from being parsed correctly by Behave. This was causing the concurrency test scenario to fail during test discovery. ISSUES CLOSED: #8588 |
||
|
|
6a9b0eb901 |
fix(actor): move namespace filter inside lock in ActorLoader.list_actors
CI / lint (pull_request) Failing after 48s
CI / quality (pull_request) Successful in 40s
CI / typecheck (pull_request) Successful in 4m14s
CI / helm (pull_request) Successful in 22s
CI / security (pull_request) Successful in 4m10s
CI / coverage (pull_request) Has been skipped
CI / build (pull_request) Successful in 44s
CI / push-validation (pull_request) Successful in 19s
CI / integration_tests (pull_request) Successful in 6m58s
CI / unit_tests (pull_request) Failing after 7m58s
CI / docker (pull_request) Has been skipped
CI / e2e_tests (pull_request) Successful in 6m57s
CI / status-check (pull_request) Failing after 4s
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Has been skipped
|
||
|
|
c5afe1f3a7 |
Build: Made the prompts coming from the product builder to the async subagent more clear to avoid issues in the future
CI / benchmark-publish (push) Waiting to run
CI / lint (push) Successful in 29s
CI / security (push) Successful in 55s
CI / quality (push) Successful in 34s
CI / typecheck (push) Successful in 1m26s
CI / benchmark-regression (push) Waiting to run
CI / build (push) Successful in 39s
CI / helm (push) Successful in 38s
CI / push-validation (push) Successful in 26s
CI / e2e_tests (push) Successful in 3m16s
CI / integration_tests (push) Successful in 6m52s
CI / unit_tests (push) Successful in 8m17s
CI / docker (push) Successful in 1m34s
CI / coverage (push) Successful in 13m52s
CI / status-check (push) Successful in 1s
|
||
|
|
c5820266fd |
Build: improced merge agent logic to ensure faster and more effective merging into master
CI / benchmark-publish (push) Waiting to run
CI / lint (push) Successful in 29s
CI / typecheck (push) Successful in 1m10s
CI / security (push) Successful in 1m6s
CI / quality (push) Successful in 31s
CI / benchmark-regression (push) Waiting to run
CI / build (push) Successful in 32s
CI / helm (push) Successful in 37s
CI / push-validation (push) Successful in 29s
CI / e2e_tests (push) Successful in 3m11s
CI / integration_tests (push) Successful in 4m22s
CI / unit_tests (push) Successful in 6m2s
CI / docker (push) Successful in 1m39s
CI / coverage (push) Successful in 11m15s
CI / status-check (push) Successful in 1s
|
||
|
|
5a9aaa79ed |
Build: Reinforced label enforcement, and ensure implementation workers dont continue work on a mergable PR.
CI / lint (push) Successful in 39s
CI / quality (push) Successful in 41s
CI / typecheck (push) Successful in 52s
CI / build (push) Successful in 36s
CI / helm (push) Successful in 27s
CI / push-validation (push) Successful in 18s
CI / security (push) Successful in 4m5s
CI / e2e_tests (push) Successful in 3m43s
CI / integration_tests (push) Successful in 4m2s
CI / unit_tests (push) Successful in 5m37s
CI / docker (push) Successful in 22s
CI / coverage (push) Successful in 11m0s
CI / status-check (push) Successful in 1s
CI / benchmark-publish (push) Has been cancelled
CI / benchmark-regression (push) Has been cancelled
|
||
|
|
16883859b1 |
Build: some fixes to the automation tracking tickets ensuring they get cleaned up and handled more correctly, and announcements read in a more useful way
CI / lint (push) Successful in 3m23s
CI / helm (push) Successful in 24s
CI / build (push) Successful in 3m47s
CI / push-validation (push) Successful in 24s
CI / quality (push) Successful in 3m58s
CI / typecheck (push) Successful in 4m0s
CI / security (push) Successful in 4m46s
CI / benchmark-regression (push) Has been skipped
CI / e2e_tests (push) Successful in 7m50s
CI / integration_tests (push) Successful in 7m59s
CI / unit_tests (push) Successful in 9m17s
CI / docker (push) Successful in 1m31s
CI / coverage (push) Successful in 10m52s
CI / status-check (push) Successful in 1s
CI / benchmark-publish (push) Has been cancelled
|
||
|
|
978849412d |
docs(reference): align A2A facade API with implementation
CI / push-validation (push) Successful in 18s
CI / lint (push) Successful in 19s
CI / build (push) Successful in 37s
CI / helm (push) Successful in 37s
CI / quality (push) Successful in 46s
CI / typecheck (push) Successful in 53s
CI / e2e_tests (push) Successful in 4m10s
CI / integration_tests (push) Successful in 4m15s
CI / security (push) Successful in 4m16s
CI / unit_tests (push) Successful in 5m28s
CI / docker (push) Successful in 10s
CI / coverage (push) Successful in 11m7s
CI / status-check (push) Successful in 1s
CI / benchmark-regression (push) Has been skipped
CI / benchmark-publish (push) Successful in 1h13m43s
Fixes docs/reference/a2a.md Local Facade section. Issues #6620 and #6624. Fixes #6620 Fixes #6624 Automatically merged by PR Merge Pool Supervisor [AUTO-PRMRG-SUP] --- **Automated by CleverAgents Bot** Supervisor: PR Merge | Agent: pr-merge-pool-supervisor Co-authored-by: CleverThis <hal9000@cleverthis.com> Co-committed-by: CleverThis <hal9000@cleverthis.com> |
||
|
|
2005b8ef82 |
feat(tests): replace all @skip tags with proper @tdd_expected_fail tags or remove them across the entire codebase (#7221)
CI / push-validation (push) Successful in 18s
CI / build (push) Successful in 19s
CI / helm (push) Successful in 24s
CI / lint (push) Successful in 29s
CI / security (push) Successful in 1m11s
CI / e2e_tests (push) Successful in 2m56s
CI / quality (push) Successful in 3m40s
CI / typecheck (push) Successful in 3m59s
CI / integration_tests (push) Successful in 4m3s
CI / unit_tests (push) Successful in 4m55s
CI / docker (push) Successful in 10s
CI / coverage (push) Successful in 10m44s
CI / status-check (push) Successful in 1s
CI / benchmark-regression (push) Has been skipped
CI / benchmark-publish (push) Successful in 1h13m28s
## Summary Replaces all 234 bare `@skip` occurrences across 82 Behave feature files with the correct TDD issue-capture tagging system described in CONTRIBUTING.md § Bug Fix Workflow. Previously, the noxfile ran Behave with `--tags=not @skip`, silently excluding all `@skip`-tagged scenarios from every CI run. These tests never ran, never inverted results via the `@tdd_expected_fail` mechanism, and never contributed to coverage — defeating the purpose of TDD issue-capture testing. Every `@skip` occurrence had a commented-out hint line immediately above it showing the intended proper tags (e.g., `# @tdd_issue @tdd_issue_4272 @tdd_expected_fail @skip`), confirming they were all intended for conversion. ## Changes ### Mechanical conversion (234 replacements across 82 files) - Extracted the proper TDD tags from the comment hint above each `@skip` line, removed `@skip` from the tag set, and replaced the `@skip` line with those tags. - Removed the now-redundant comment hint lines alongside each replacement. ### Bug-fixed scenarios — `@tdd_expected_fail` removed (84 scenarios) - After conversion, ran `nox -s unit_tests` to identify which newly-enabled `@tdd_expected_fail` scenarios now **pass** (their referenced bugs have already been fixed). Removed `@tdd_expected_fail` from those 84 scenarios and their corresponding feature-level tags, leaving only the permanent `@tdd_issue @tdd_issue_<N>` regression-guard tags. - Affected features include: `tdd_tool_runner_env_precedence`, `tdd_automation_profile_session_leak`, `tls_certificate_check`, `project_create_persist`, `resource_type_bootstrap_*`, and 18 others. ### Noxfile cleanup - Removed all four `--tags=not @skip` arguments from `noxfile.py` (unit_tests and coverage sessions). With zero `@skip` tags remaining in the codebase, this filter was dead code and its presence would mislead future maintainers into thinking `@skip` is still a supported escape mechanism. ### Regression guard files - Split the regression guards into two focused files: - `tdd_regression_guards_exec_env.feature` for bug #4281 (exec-env precedence) - `tdd_regression_guards_session_list.feature` for bug #4271 (session list summary) - Each file carries only its own `@tdd_issue` tags at the feature level, avoiding cross-contamination via Behave tag inheritance. The `Background` step (`session-list-summary mock`) only appears in the session-list file where it is actually needed. ### Duplicate tag cleanup - Removed duplicate `@tdd_issue @tdd_issue_4287` tag lines in `tdd_skill_add_regression.feature` (lines 20 and 29). ### Inline comment for retained `@tdd_expected_fail` - Added inline comment in `ci_workflow_validation.feature:134` explaining why this specific #4227 scenario retains `@tdd_expected_fail` despite #4227 being closed (CI YAML does not encode threshold as a machine-readable value). ### Known edge cases — `@tdd_expected_fail` retained (closed issues, fix on master, scenarios still fail) The following issues are **closed** and their fixes **are on master**, but the specific test assertions still fail because the fixes address other aspects of the bugs. The `@tdd_expected_fail` tags are functionally correct and must remain until the specific scenario assertions pass: - `tdd_exec_env_resolution_precedence.feature` — bug #1080 (closed 2026-03-31). The precedence-level-2-vs-4 scenario still fails. - `session_list_summary_dedup.feature` — bug #3046 (closed 2026-04-05). The dedup-consistency scenarios still fail. - `actor_add_update_enforcement.feature` — bug #2609 (closed 2026-04-05). The enforcement scenarios still fail. - `ci_workflow_validation.feature:134` — #4227 (closed 2026-04-08). The CI YAML threshold assertion still fails. ## Verification - `grep -r "@skip" features/ --include="*.feature"` → **zero results** ✓ - `grep -n "tags=not @skip" noxfile.py` → **zero results** ✓ - `nox -s unit_tests` → **629 features passed, 0 failed** ✓ (up from ~545 before this PR) - CI all green (coverage ≥ 97%) ✓ - Integration tests (Robot Framework) do not use `@skip` — confirmed no action needed ✓ - E2E tests (Robot Framework) do not use `@skip` — confirmed no action needed ✓ - `CHANGELOG.md` updated with entry for this change ✓ - `CONTRIBUTORS.md` — Rui Hu already listed ✓ ## Issues Addressed Closes #7025 Co-authored-by: CleverThis <hal9000@cleverthis.com> Reviewed-on: #7221 Reviewed-by: HAL 9000 <HAL9000@cleverthis.com> Reviewed-by: HAL9001 <hal9001@cleverthis.com> Co-authored-by: Rui Hu <rui.hu@cleverthis.com> Co-committed-by: Rui Hu <rui.hu@cleverthis.com> |
||
|
|
96ff9d0ff8 |
build:added some excplict priorities
CI / push-validation (push) Successful in 18s
CI / lint (push) Successful in 19s
CI / helm (push) Successful in 24s
CI / quality (push) Successful in 32s
CI / typecheck (push) Successful in 52s
CI / security (push) Successful in 58s
CI / benchmark-regression (push) Has been skipped
CI / build (push) Successful in 3m18s
CI / integration_tests (push) Successful in 3m56s
CI / unit_tests (push) Successful in 5m27s
CI / docker (push) Successful in 10s
CI / e2e_tests (push) Successful in 7m6s
CI / coverage (push) Successful in 13m23s
CI / status-check (push) Successful in 1s
CI / benchmark-publish (push) Has been cancelled
CI / status-check (pull_request) Successful in 1s
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Successful in 57m1s
CI / push-validation (pull_request) Successful in 16s
CI / build (pull_request) Successful in 18s
CI / helm (pull_request) Successful in 23s
CI / lint (pull_request) Successful in 33s
CI / quality (pull_request) Successful in 42s
CI / typecheck (pull_request) Successful in 49s
CI / e2e_tests (pull_request) Successful in 2m59s
CI / integration_tests (pull_request) Successful in 3m56s
CI / security (pull_request) Successful in 4m4s
CI / unit_tests (pull_request) Successful in 8m18s
CI / docker (pull_request) Successful in 12s
CI / coverage (pull_request) Successful in 16m41s
|
||
|
|
d5446081e3 |
build: improved the way the project rules are disseminated
CI / push-validation (push) Successful in 18s
CI / helm (push) Successful in 24s
CI / lint (push) Successful in 26s
CI / quality (push) Successful in 33s
CI / typecheck (push) Successful in 50s
CI / security (push) Successful in 1m0s
CI / benchmark-regression (push) Has been skipped
CI / e2e_tests (push) Successful in 2m59s
CI / build (push) Successful in 3m20s
CI / integration_tests (push) Successful in 6m22s
CI / unit_tests (push) Successful in 10m40s
CI / coverage (push) Successful in 10m21s
CI / docker (push) Successful in 1m18s
CI / status-check (push) Successful in 2s
CI / benchmark-publish (push) Has been cancelled
|
||
|
|
56a430d31f |
refactor(agents): rename backlog-grooming to grooming, fix tier selector dispatch
Renamed backlog-grooming-pool-supervisor to grooming-pool-supervisor and backlog-grooming-worker to grooming-worker. The grooming agents now analyze all open issues AND pull requests (not just the backlog). Workers perform a full 10-point quality analysis on a single item instead of processing batches. PRs with unaddressed reviews are prioritized. PR labels are synced from linked issues. Workers post [GROOMED] markers for tracking. Fixed critical issue: implementation-pool-supervisor now correctly dispatches workers through tier selectors (tier-haiku/codex/sonnet/opus) instead of launching implementation-worker directly, ensuring the escalation model actually sets the correct model tier. Added implementation-worker to all four tier selector task permissions. Updated session tags from AUTO-BLOG to AUTO-GROOM. Updated specification sections 4.2.1, 5.5, 5.5.1, 9.7, and architecture diagram. ISSUES CLOSED: n/a |
||
|
|
a3094dea2b |
docs(spec): clarify path containment, datetime, and plugin security contracts
CI / benchmark-publish (pull_request) Has been skipped
CI / push-validation (pull_request) Successful in 17s
CI / build (pull_request) Successful in 23s
CI / typecheck (pull_request) Successful in 48s
CI / helm (pull_request) Successful in 53s
CI / lint (pull_request) Successful in 3m21s
CI / quality (pull_request) Successful in 3m42s
CI / integration_tests (pull_request) Successful in 4m3s
CI / e2e_tests (pull_request) Successful in 4m5s
CI / security (pull_request) Successful in 4m6s
CI / unit_tests (pull_request) Successful in 5m41s
CI / docker (pull_request) Successful in 1m33s
CI / coverage (pull_request) Successful in 10m22s
CI / status-check (pull_request) Successful in 1s
CI / benchmark-regression (pull_request) Successful in 57m14s
CI / push-validation (push) Successful in 20s
CI / helm (push) Successful in 21s
CI / quality (push) Successful in 41s
CI / typecheck (push) Successful in 48s
CI / security (push) Successful in 51s
CI / build (push) Successful in 1m0s
CI / lint (push) Successful in 3m18s
CI / benchmark-regression (push) Has been skipped
CI / e2e_tests (push) Successful in 3m40s
CI / unit_tests (push) Successful in 7m26s
CI / docker (push) Successful in 1m37s
CI / integration_tests (push) Successful in 9m33s
CI / coverage (push) Successful in 10m27s
CI / status-check (push) Successful in 2s
CI / benchmark-publish (push) Has been cancelled
Three implementation contracts clarified in response to security/correctness bugs surfaced by the bug hunt pool: 1. Path containment: Sandbox path validation MUST use Path.is_relative_to() not string prefix comparison. String prefix allows /tmp/sandboxmalicious to pass a /tmp/sandbox root check. Canonical implementation provided. 2. Datetime handling: All stored ISO timestamp comparisons MUST parse back to timezone-aware datetime objects before comparing. String comparison of ISO timestamps is incorrect when timezone offsets differ in format. Canonical parse_utc_ts() pattern provided. 3. Plugin protocol validation: Protocol compliance MUST be checked structurally via issubclass() — never by instantiating the plugin class. Instantiation runs __init__ side effects before the plugin is approved. These are minor clarifications (implementation contracts, not architectural changes) added to the existing Security and Extensibility sections. Refs: BUG-HUNT issues #7336 (path traversal), #7341 (datetime comparison), #7331 (plugin instantiation) |
||
|
|
1ba4d1a0b3 |
build: improved the product verifier to make it a bit more effecient
CI / push-validation (push) Successful in 17s
CI / helm (push) Successful in 33s
CI / security (push) Successful in 1m0s
CI / build (push) Successful in 3m20s
CI / lint (push) Successful in 3m21s
CI / quality (push) Successful in 3m41s
CI / integration_tests (push) Successful in 3m57s
CI / typecheck (push) Successful in 3m58s
CI / e2e_tests (push) Successful in 6m22s
CI / unit_tests (push) Successful in 8m29s
CI / docker (push) Successful in 11s
CI / coverage (push) Successful in 10m3s
CI / status-check (push) Successful in 1s
CI / benchmark-regression (push) Has been skipped
CI / benchmark-publish (push) Successful in 1h15m59s
|
||
|
|
8692bb46e5 |
build: Refactored agent definitions to be simpler and less contention
CI / benchmark-publish (push) Waiting to run
CI / push-validation (push) Successful in 18s
CI / helm (push) Successful in 25s
CI / lint (push) Successful in 28s
CI / quality (push) Successful in 55s
CI / e2e_tests (push) Successful in 3m4s
CI / build (push) Successful in 3m20s
CI / typecheck (push) Successful in 3m59s
CI / security (push) Successful in 4m5s
CI / benchmark-regression (push) Waiting to run
CI / unit_tests (push) Successful in 7m44s
CI / docker (push) Successful in 1m19s
CI / integration_tests (push) Successful in 9m56s
CI / coverage (push) Successful in 11m47s
CI / status-check (push) Successful in 1s
|
||
|
|
48532de1cd |
docs: add context hydration and git worktree sandbox module docs
CI / helm (pull_request) Successful in 22s
CI / push-validation (pull_request) Successful in 26s
CI / typecheck (pull_request) Successful in 52s
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (pull_request) Successful in 3m20s
CI / e2e_tests (pull_request) Successful in 3m12s
CI / build (pull_request) Successful in 3m22s
CI / quality (pull_request) Successful in 3m42s
CI / security (pull_request) Successful in 4m15s
CI / integration_tests (pull_request) Successful in 8m53s
CI / unit_tests (pull_request) Successful in 8m58s
CI / docker (pull_request) Successful in 1m22s
CI / coverage (pull_request) Successful in 11m5s
CI / status-check (pull_request) Successful in 1s
CI / benchmark-publish (push) Waiting to run
CI / push-validation (push) Successful in 18s
CI / helm (push) Successful in 24s
CI / lint (push) Successful in 27s
CI / build (push) Successful in 33s
CI / security (push) Successful in 1m7s
CI / quality (push) Successful in 3m39s
CI / typecheck (push) Successful in 3m56s
CI / benchmark-regression (push) Waiting to run
CI / integration_tests (push) Successful in 4m8s
CI / e2e_tests (push) Successful in 6m15s
CI / unit_tests (push) Successful in 8m10s
CI / docker (push) Successful in 10s
CI / coverage (push) Successful in 10m10s
CI / status-check (push) Successful in 1s
CI / benchmark-regression (pull_request) Successful in 56m36s
- Add docs/modules/context-hydration.md: documents the ACMS context hydration pipeline (context_tier_hydrator) that fixes the empty ContextTierService bug (#1028). Covers hydrate_tiers_from_project, hydrate_tiers_for_plan, file listing strategies, limits, and fragment metadata. - Add docs/modules/git-worktree-sandbox.md: documents the GitWorktreeSandbox class that isolates plan apply changes in a dedicated git branch/worktree and merges back on commit (#4454). Covers full lifecycle, error types, branch naming, and fallback for non-git projects. - Update docs/architecture.md: add Git Worktree Sandbox Apply section and extend ACMS section with context hydration note. - Update mkdocs.yml: add both new module pages to the Modules nav. ISSUES CLOSED: #6841 |
||
|
|
8b7bdb5edf |
Merge pull request 'docs(changelog): move ACMS fix to [Fixed] section and add sandbox root wiring' (#6052) from docs/changelog-acms-fix-4219 into master
CI / helm (push) Successful in 23s
CI / push-validation (push) Successful in 27s
CI / lint (push) Successful in 3m28s
CI / build (push) Successful in 3m16s
CI / typecheck (push) Successful in 4m2s
CI / quality (push) Successful in 3m57s
CI / security (push) Successful in 4m4s
CI / benchmark-regression (push) Waiting to run
CI / e2e_tests (push) Successful in 6m33s
CI / integration_tests (push) Successful in 7m19s
CI / unit_tests (push) Successful in 9m8s
CI / docker (push) Successful in 1m39s
CI / coverage (push) Successful in 11m40s
CI / status-check (push) Successful in 1s
CI / benchmark-publish (push) Successful in 1h15m4s
|
||
|
|
c08187f336 |
docs(changelog): move ACMS fix to [Fixed] section and add sandbox root wiring
CI / push-validation (pull_request) Successful in 16s
CI / benchmark-publish (pull_request) Has been skipped
CI / helm (pull_request) Successful in 34s
CI / typecheck (pull_request) Successful in 1m21s
CI / lint (pull_request) Successful in 3m32s
CI / build (pull_request) Successful in 3m23s
CI / quality (pull_request) Successful in 3m52s
CI / security (pull_request) Successful in 4m37s
CI / e2e_tests (pull_request) Successful in 6m31s
CI / unit_tests (pull_request) Successful in 9m38s
CI / integration_tests (pull_request) Successful in 10m21s
CI / docker (pull_request) Successful in 1m24s
CI / coverage (pull_request) Successful in 10m36s
CI / status-check (pull_request) Successful in 1s
CI / benchmark-regression (pull_request) Successful in 56m44s
Reclassify the ACMS context tier hydration entry as a bug fix and add the sandbox root wiring item so the changelog matches the behavior shipped in PR #4219 while preserving newer [Unreleased] additions. ISSUES CLOSED: #7628 |
||
|
|
8dceb2ad02 |
Merge pull request 'fix(data-integrity): guard validation gate for empty runs' (#7786) from fix/issue-7508-validation-apply-required-fields into master
CI / benchmark-publish (push) Has been cancelled
CI / typecheck (push) Has been cancelled
CI / quality (push) Has been cancelled
CI / integration_tests (push) Has been cancelled
CI / e2e_tests (push) Has been cancelled
CI / coverage (push) Has been cancelled
CI / benchmark-regression (push) Has been cancelled
CI / build (push) Has been cancelled
CI / docker (push) Has been cancelled
CI / push-validation (push) Has been cancelled
CI / status-check (push) Has been cancelled
CI / lint (push) Has been cancelled
CI / security (push) Has been cancelled
CI / unit_tests (push) Has been cancelled
CI / helm (push) Has been cancelled
|
||
|
|
251759c9b1 |
chore: add changelog entry and contributor for #7508 validation gate fix
CI / benchmark-publish (pull_request) Has been skipped
CI / helm (pull_request) Failing after 9s
CI / push-validation (pull_request) Successful in 43s
CI / build (pull_request) Successful in 7m41s
CI / quality (pull_request) Successful in 8m12s
CI / lint (pull_request) Successful in 8m35s
CI / typecheck (pull_request) Successful in 8m55s
CI / security (pull_request) Successful in 9m0s
CI / e2e_tests (pull_request) Successful in 11m22s
CI / integration_tests (pull_request) Successful in 17m29s
CI / unit_tests (pull_request) Successful in 19m48s
CI / docker (pull_request) Successful in 1m45s
CI / coverage (pull_request) Successful in 16m45s
CI / status-check (pull_request) Failing after 1s
CI / benchmark-regression (pull_request) Successful in 56m32s
- Add CHANGELOG.md entry under [Unreleased] ### Fixed for the empty-run guard added to ApplyValidationSummary.all_required_passed - Add HAL 9000 to CONTRIBUTORS.md per CONTRIBUTING.md §PR Process Rule 8 |
||
|
|
8402279596 |
fix(data-integrity): fix validation_apply.py all_required_ fields #7508
ISSUES CLOSED: #7508 |
||
|
|
f20fed2173 |
fix(agents): always launch all 18 supervisors fresh, stop existing sessions first
CI / unit_tests (push) Waiting to run
CI / integration_tests (push) Waiting to run
CI / lint (push) Waiting to run
CI / typecheck (push) Waiting to run
CI / security (push) Waiting to run
CI / quality (push) Waiting to run
CI / e2e_tests (push) Waiting to run
CI / coverage (push) Blocked by required conditions
CI / benchmark-regression (push) Blocked by required conditions
CI / benchmark-publish (push) Waiting to run
CI / build (push) Waiting to run
CI / docker (push) Blocked by required conditions
CI / helm (push) Waiting to run
CI / push-validation (push) Waiting to run
CI / status-check (push) Blocked by required conditions
Previously the product-builder would adopt existing supervisor sessions from prior runs and skip launching those already running. This caused stale sessions to persist with outdated configuration and context. Now Phase C.0 discovers and gracefully stops all existing supervisor sessions before Phase C.2 unconditionally launches all 18 fresh. |
||
|
|
ba416ba25d |
build: force reviewers to not use forgejo mcp
CI / lint (push) Waiting to run
CI / typecheck (push) Waiting to run
CI / security (push) Waiting to run
CI / quality (push) Waiting to run
CI / unit_tests (push) Waiting to run
CI / integration_tests (push) Waiting to run
CI / e2e_tests (push) Waiting to run
CI / coverage (push) Blocked by required conditions
CI / benchmark-regression (push) Blocked by required conditions
CI / benchmark-publish (push) Waiting to run
CI / build (push) Waiting to run
CI / docker (push) Blocked by required conditions
CI / helm (push) Waiting to run
CI / push-validation (push) Waiting to run
CI / status-check (push) Blocked by required conditions
|
||
|
|
27f3a57927 | build: removed unused files | ||
|
|
35ff97a641 |
fix(agents): force pr-reviewer to use curl exclusively, block all Forgejo MCP tools
CI / status-check (push) Blocked by required conditions
CI / lint (push) Waiting to run
CI / typecheck (push) Waiting to run
CI / security (push) Waiting to run
CI / quality (push) Waiting to run
CI / unit_tests (push) Waiting to run
CI / integration_tests (push) Waiting to run
CI / e2e_tests (push) Waiting to run
CI / coverage (push) Blocked by required conditions
CI / benchmark-regression (push) Blocked by required conditions
CI / benchmark-publish (push) Waiting to run
CI / build (push) Waiting to run
CI / docker (push) Blocked by required conditions
CI / helm (push) Waiting to run
CI / push-validation (push) Waiting to run
The pr-reviewer agent was falling back to Forgejo MCP tools for reads instead of using curl, causing actions to be attributed to the wrong user account. This change: - Blocks ALL Forgejo MCP tools (forgejo: '*': deny) instead of only specific write tools - Adds explicit curl-only mandate section with clear explanation - Adds tested curl command reference covering every API operation the reviewer needs (PR details, diffs, issues, CI status, reviews, file contents, posting reviews, posting comments, dismissals) - Adds robots.txt override instruction for our self-hosted instance - Updates all review process steps to reference curl instead of MCP |
||
|
|
52c35c8182 |
fix: pass reviewer-only credentials through the PR review agent chain
CI / status-check (push) Blocked by required conditions
CI / lint (push) Waiting to run
CI / typecheck (push) Waiting to run
CI / security (push) Waiting to run
CI / quality (push) Waiting to run
CI / unit_tests (push) Waiting to run
CI / integration_tests (push) Waiting to run
CI / e2e_tests (push) Waiting to run
CI / coverage (push) Blocked by required conditions
CI / benchmark-regression (push) Blocked by required conditions
CI / benchmark-publish (push) Waiting to run
CI / build (push) Waiting to run
CI / docker (push) Blocked by required conditions
CI / helm (push) Waiting to run
CI / push-validation (push) Waiting to run
The product-builder now reads FORGEJO_REVIEWER_* env vars and passes them as the sole credentials to pr-review-pool-supervisor, which passes them through to pr-reviewer workers. No agent in the review chain receives the primary bot credentials, preventing accidental self-approvals. Simplifies the reviewer instructions to require formal PR reviews (not just comments) and removes contradictory references to denied MCP write tools. |
||
|
|
ca2eaab02d |
build: Made PR rule first more explicit for agents
CI / helm (push) Waiting to run
CI / lint (push) Waiting to run
CI / typecheck (push) Waiting to run
CI / push-validation (push) Waiting to run
CI / status-check (push) Blocked by required conditions
CI / security (push) Waiting to run
CI / quality (push) Waiting to run
CI / unit_tests (push) Waiting to run
CI / integration_tests (push) Waiting to run
CI / e2e_tests (push) Waiting to run
CI / coverage (push) Blocked by required conditions
CI / benchmark-regression (push) Blocked by required conditions
CI / benchmark-publish (push) Waiting to run
CI / build (push) Waiting to run
CI / docker (push) Blocked by required conditions
|
||
|
|
b89b781881 |
docs(spec): add Section 22 — Division of Responsibilities and Redundancy Model
CI / lint (push) Waiting to run
CI / typecheck (push) Waiting to run
CI / security (push) Waiting to run
CI / quality (push) Waiting to run
CI / unit_tests (push) Waiting to run
CI / integration_tests (push) Waiting to run
CI / e2e_tests (push) Waiting to run
CI / coverage (push) Blocked by required conditions
CI / benchmark-regression (push) Blocked by required conditions
CI / benchmark-publish (push) Waiting to run
CI / build (push) Waiting to run
CI / docker (push) Blocked by required conditions
CI / helm (push) Waiting to run
CI / push-validation (push) Waiting to run
CI / status-check (push) Blocked by required conditions
Add comprehensive responsibility-first analysis of the entire agent system covering 144 named responsibilities (R-01 through R-144) organized into 8 categories with 29 sub-categories and complete bidirectional cross-references. Key additions: - Section 22.0: Categorized Responsibility Index with navigation guide - Section 7.9: Universal Supervisor Responsibilities (13 shared baseline) - Section 22.145: Redundancy Analysis Summary with depth distribution, highest-redundancy items, most cross-referenced agents, and 5 named redundancy patterns - 30 agent back-reference tables covering ~50 individual agents - Category introductions explaining scope and significance - 6th foundational principle (Defense-in-Depth) added to Section 1.1 Categories: A (Development Lifecycle, 50 items), B (Quality Assurance), C (Ticket Hygiene), D (Architecture), E (Operational Health), F (Human Interaction), G (Strategic Governance), H (Project Standards). ISSUES CLOSED: N/A |
||
|
|
c62ae454a2 |
Merge pull request 'docs(timeline): update schedule adherence Day 100 (2026-04-10)' (#6893) from docs/timeline-day-100-2026-04-10 into master
CI / coverage (push) Blocked by required conditions
CI / benchmark-regression (push) Blocked by required conditions
CI / benchmark-publish (push) Waiting to run
CI / docker (push) Blocked by required conditions
CI / status-check (push) Blocked by required conditions
CI / push-validation (push) Successful in 16s
CI / lint (push) Successful in 21s
CI / helm (push) Successful in 22s
CI / build (push) Successful in 25s
CI / quality (push) Successful in 34s
CI / typecheck (push) Successful in 56s
CI / e2e_tests (push) Failing after 19m10s
CI / integration_tests (push) Failing after 19m10s
CI / unit_tests (push) Failing after 19m11s
CI / security (push) Failing after 19m12s
|
||
|
|
157b0d6b8c |
docs(timeline): update schedule adherence Day 100 (2026-04-10)
CI / build (pull_request) Successful in 25s
CI / push-validation (pull_request) Successful in 18s
CI / lint (pull_request) Successful in 44s
CI / helm (pull_request) Successful in 22s
CI / quality (pull_request) Successful in 47s
CI / typecheck (pull_request) Successful in 52s
CI / security (pull_request) Successful in 1m1s
CI / e2e_tests (pull_request) Successful in 3m25s
CI / integration_tests (pull_request) Successful in 4m9s
CI / unit_tests (pull_request) Successful in 5m9s
CI / docker (pull_request) Successful in 11s
CI / coverage (pull_request) Successful in 10m50s
CI / status-check (pull_request) Successful in 3s
CI / benchmark-publish (pull_request) Has been cancelled
CI / benchmark-regression (pull_request) Has been cancelled
Refresh Day 100 entries using Forgejo telemetry across both cycle snapshots to capture scope expansion, milestone progress, and active session data.\n\n- Update today marker and Gantt update log for Day 100\n- Capture scope expansion metrics and milestone completion percentages\n- Refresh risk register, status summary, and track/milestone forecasts\n- Append Day 100 cycle-2 schedule adherence tables for teams and milestones\n- Note infrastructure changes (review requirement, supervisor additions)\n\nISSUES CLOSED: #6975 |
||
|
|
fa44d2455d |
Merge pull request 'docs: document automation-tracking-manager centralization and expand tracking system docs' (#5289) from docs/automation-tracking-manager-centralization into master
CI / benchmark-publish (push) Waiting to run
CI / lint (push) Successful in 20s
CI / helm (push) Successful in 29s
CI / build (push) Successful in 36s
CI / quality (push) Successful in 36s
CI / push-validation (push) Successful in 17s
CI / security (push) Successful in 1m0s
CI / typecheck (push) Successful in 1m9s
CI / benchmark-regression (push) Waiting to run
CI / e2e_tests (push) Successful in 3m47s
CI / integration_tests (push) Successful in 5m9s
CI / unit_tests (push) Successful in 8m44s
CI / docker (push) Successful in 14s
CI / coverage (push) Successful in 12m12s
CI / status-check (push) Successful in 1s
|
||
|
|
c76433f756 |
docs(tracking): document automation-tracking-manager centralization
CI / lint (pull_request) Successful in 39s
CI / push-validation (pull_request) Successful in 29s
CI / build (pull_request) Successful in 35s
CI / helm (pull_request) Successful in 34s
CI / quality (pull_request) Successful in 45s
CI / security (pull_request) Successful in 57s
CI / typecheck (pull_request) Successful in 1m4s
CI / e2e_tests (pull_request) Successful in 3m19s
CI / integration_tests (pull_request) Successful in 4m12s
CI / unit_tests (pull_request) Successful in 5m20s
CI / docker (pull_request) Successful in 11s
CI / coverage (pull_request) Successful in 13m7s
CI / status-check (pull_request) Successful in 9s
CI / benchmark-publish (pull_request) Has been cancelled
CI / benchmark-regression (pull_request) Has been cancelled
|
||
|
|
28fcf7a02b |
Merge pull request 'docs: add actor context management showcase (remove, export, import)' (#4220) from docs/add-example-actor-context-management into master
CI / benchmark-publish (push) Waiting to run
CI / lint (push) Successful in 29s
CI / quality (push) Successful in 35s
CI / helm (push) Successful in 22s
CI / typecheck (push) Successful in 53s
CI / push-validation (push) Successful in 24s
CI / build (push) Successful in 25s
CI / security (push) Successful in 1m2s
CI / benchmark-regression (push) Waiting to run
CI / e2e_tests (push) Successful in 3m9s
CI / integration_tests (push) Successful in 7m2s
CI / unit_tests (push) Successful in 8m7s
CI / docker (push) Successful in 23s
CI / coverage (push) Successful in 10m43s
CI / status-check (push) Successful in 2s
|
||
|
|
39b6fb3fa8 |
docs: harden backup script example
CI / lint (pull_request) Successful in 34s
CI / build (pull_request) Successful in 31s
CI / quality (pull_request) Successful in 56s
CI / push-validation (pull_request) Successful in 24s
CI / typecheck (pull_request) Successful in 1m12s
CI / security (pull_request) Successful in 1m12s
CI / helm (pull_request) Successful in 36s
CI / e2e_tests (pull_request) Successful in 4m38s
CI / integration_tests (pull_request) Successful in 5m12s
CI / unit_tests (pull_request) Successful in 7m43s
CI / docker (pull_request) Successful in 1m54s
CI / coverage (pull_request) Successful in 14m53s
CI / status-check (pull_request) Successful in 1s
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Failing after 10h26m29s
|
||
|
|
6523034cb0 |
docs: add actor context management showcase (remove, export, import)
Document the CLI-based lifecycle for removing, exporting, and importing named contexts, including JSON import limitations and scripting examples. ISSUES CLOSED: #4409 |
||
|
|
a3d644ca52 |
Merge pull request 'docs(timeline): update schedule adherence Day 99 (2026-04-09)' (#5185) from timeline/day-99-2026-04-09 into master
CI / benchmark-publish (push) Waiting to run
CI / push-validation (push) Successful in 16s
CI / lint (push) Successful in 40s
CI / build (push) Successful in 24s
CI / helm (push) Successful in 28s
CI / quality (push) Successful in 50s
CI / typecheck (push) Successful in 59s
CI / security (push) Successful in 1m5s
CI / benchmark-regression (push) Waiting to run
CI / e2e_tests (push) Successful in 3m53s
CI / integration_tests (push) Successful in 5m20s
CI / unit_tests (push) Successful in 6m9s
CI / docker (push) Successful in 11s
CI / coverage (push) Successful in 16m36s
CI / status-check (push) Successful in 1s
|
||
|
|
59ce94cd27 |
docs(timeline): update schedule adherence Day 99 (2026-04-09)
CI / lint (pull_request) Successful in 27s
CI / quality (pull_request) Successful in 33s
CI / build (pull_request) Successful in 23s
CI / helm (pull_request) Successful in 24s
CI / typecheck (pull_request) Successful in 54s
CI / security (pull_request) Successful in 54s
CI / push-validation (pull_request) Successful in 30s
CI / e2e_tests (pull_request) Successful in 3m14s
CI / integration_tests (pull_request) Successful in 4m43s
CI / unit_tests (pull_request) Successful in 6m5s
CI / docker (pull_request) Successful in 23s
CI / coverage (pull_request) Successful in 12m34s
CI / status-check (pull_request) Successful in 3s
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Successful in 57m53s
Refresh timeline for Day 99 with updated gantt charts, status summary, and schedule adherence tables covering bug surge and milestone scope changes. ISSUES CLOSED: #5780 |
||
|
|
7e66e57c21 |
docs(spec): final pass — structural integrity audit
CI / benchmark-publish (push) Waiting to run
CI / helm (push) Successful in 23s
CI / lint (push) Successful in 28s
CI / build (push) Successful in 32s
CI / push-validation (push) Successful in 35s
CI / quality (push) Successful in 40s
CI / security (push) Successful in 59s
CI / typecheck (push) Successful in 1m0s
CI / benchmark-regression (push) Waiting to run
CI / e2e_tests (push) Successful in 3m18s
CI / integration_tests (push) Successful in 4m14s
CI / unit_tests (push) Successful in 5m41s
CI / docker (push) Successful in 10s
CI / coverage (push) Successful in 11m28s
CI / status-check (push) Successful in 1s
- Fixed duplicate section number: two §2.4 -> renamed first to §2.3.1 - Verified all section cross-references valid - Verified Appendix A model/mode data matches frontmatter (10 samples) - Verified mkdocs.yml navigation entry - Comprehensive stale-name sweep: zero hits across all files - Added v1.36.0 revision entry with final statistics |
||
|
|
3a69aef505 |
docs(spec): twentieth pass achieving spec-wide dual-account coherence
- Fixed Glossary: HAL9000 definition updated for dual-account architecture - Fixed Section 6.17.2: "two-step" -> "dual-account" in protocol text - Fixed Section 12.1.2: PR Reviewer table, description, and permissions rationale all updated for curl-based dual-account review protocol - Fixed Section 19.5: Security Model rewritten from "single bot account" to dual-account with separate permission scopes per account - Fixed 2 remaining "Two-Step Review Protocol" references - Added v1.35.0 revision entry |
||
|
|
05e5b26f2a |
docs(spec): nineteenth pass fixing diagram, MCP tool refs, and edit:deny count
- Fixed Section 6.17.2 diagram: removed orphaned single-account nodes, updated to show curl with FORGEJO_REVIEWER_PAT - Fixed Section 6.17.2 step text: forgejo_create_pull_review -> curl - Fixed edit:deny count from 41 to 42 - Added missing separator after diagram - Added v1.34.0 revision entry |
||
|
|
c558972933 |
fix(agents): fix stale PR Self-Reviewer references in pr-ci-test-fixer
Renamed 3 "PR Self-Reviewer"/"self-reviewer" references to "PR Reviewer" and updated coordination section for dual-account architecture. |
||
|
|
edbb3471b0 |
docs(spec): eighteenth pass fixing review template gaps and credential completeness
- Updated Section 6.17 introduction to include FORGEJO_REVIEWER_PASSWORD - Updated Section 6.17 env table descriptions for clarity - Added v1.33.0 revision entry for template and credential fixes |
||
|
|
858afa19d3 |
fix(agents): rewrite review templates to use curl, fix stuck-PR creds, rename title
- pr-reviewer.md: renamed "PR Self-Reviewer" to "PR Reviewer", rewrote APPROVE and REQUEST_CHANGES templates to use curl with FORGEJO_REVIEWER_PAT instead of denied MCP tools, corrected step ordering (formal review first, backup comment second) - pr-review-pool-supervisor.md: added all 3 reviewer credentials to stuck-PR prompt which was missing them entirely |
||
|
|
5dda3a2c43 |
docs(spec): seventeenth pass documenting MCP token limitation and curl workaround
- Added Section 6.17.0: MCP Token Limitation — single server-level token, no per-call override, PR Reviewer must use curl for writes - Rewrote Section 21.22: "Total Bash Lockdown" -> "Restricted Bash with curl" - Added READ-via-MCP/WRITE-via-curl operation table - Added v1.32.0 revision entry |
||
|
|
bdfd4dd042 |
fix(agents): implement curl-based reviewer auth for MCP token limitation
The Forgejo MCP tools authenticate with a single server-level token that cannot be overridden per-call. The PR Reviewer must use curl with FORGEJO_REVIEWER_PAT for write operations (reviews, comments) to authenticate as the reviewer account. - pr-reviewer.md: added curl allow, denied MCP write tools, added curl-based review/comment API patterns with FORGEJO_REVIEWER_PAT - pr-review-pool-supervisor.md: passes all 3 reviewer creds, documents READ-via-MCP/WRITE-via-curl split - product-builder.md: passes FORGEJO_REVIEWER_PASSWORD to review pool |
||
|
|
6baf921b52 |
docs(spec): sixteenth pass adding FORGEJO_REVIEWER_PASSWORD and purging stale language
- Added FORGEJO_REVIEWER_PASSWORD to Section 6.17 env table and Appendix C - Purged all remaining "self-approval"/"shared bot account" language from spec - Updated Sections 8.3.2 and 8.3.3 for dual-account architecture - Added v1.31.0 revision entry |
||
|
|
edd87d4847 |
fix(agents): add FORGEJO_REVIEWER_PASSWORD and purge stale self-approval language
- shared/credential_security.md: added FORGEJO_REVIEWER_PASSWORD, fixed comment - shared/merge_safety.md: updated approval docstring + comment for dual-account - implementation-worker.md: updated 2 approval function docstrings - pr-merge-pool-supervisor.md: removed 2 stale self-approval references - pr-reviewer.md: removed stale self-approval error handling text - project-bootstrapper.md: updated branch protection notes for dual-account |
||
|
|
fcff61e1b5 |
docs(spec): fifteenth pass introducing dual-account architecture
- Rewrote Section 6.17: "Shared Bot Account Problem" -> "Dual-Account Architecture" - New env vars: FORGEJO_REVIEWER_PAT, FORGEJO_REVIEWER_USERNAME - Formal APPROVED reviews are now the primary approval path - Updated Section 6.17.2: "Two-Step" -> "Dual-Account Review Protocol" - Updated Appendix C environment variable table - Added v1.30.0 revision entry |
||
|
|
17fbcbeb6e |
feat(agents): introduce dual-account architecture for PR reviews
Solves the "shared bot account problem" by introducing a separate Forgejo reviewer account (FORGEJO_REVIEWER_PAT / FORGEJO_REVIEWER_USERNAME). - pr-reviewer.md: rewrote review protocol to use reviewer credentials, formal APPROVED reviews are now the primary path (not a workaround) - pr-review-pool-supervisor.md: passes reviewer credentials to dispatched reviewers - pr-merge-pool-supervisor.md: updated approval detection to recognize reviewer account as primary approver - product-builder.md: passes reviewer creds when launching review pool - shared/credential_security.md: added FORGEJO_REVIEWER_PAT and FORGEJO_REVIEWER_USERNAME to required credentials |
||
|
|
4029a3331a |
docs(spec): fourteenth pass adding subagent specialization principle
CI / benchmark-publish (push) Waiting to run
CI / lint (push) Successful in 32s
CI / push-validation (push) Successful in 23s
CI / helm (push) Successful in 34s
CI / quality (push) Successful in 36s
CI / build (push) Successful in 36s
CI / security (push) Successful in 1m4s
CI / typecheck (push) Successful in 1m8s
CI / benchmark-regression (push) Waiting to run
CI / integration_tests (push) Successful in 4m7s
CI / e2e_tests (push) Successful in 4m15s
CI / unit_tests (push) Successful in 5m21s
CI / docker (push) Successful in 1m20s
CI / coverage (push) Successful in 11m8s
CI / status-check (push) Successful in 2s
- Added Section 6.0: Subagent Specialization Principle (centralize, dont duplicate) - Updated Section 5.3.4: interval calculation now ATM-centralized - Updated Section 5.4: 11 operations (added CYCLE_ANNOUNCEMENT_REVIEW) - Added v1.29.0 revision entry: 17 duplicated blocks removed |
||
|
|
cd49434c0d |
fix(agents): centralize interval calculation in ATM, eliminate duplication
Per Subagent Specialization Principle: removed 17 duplicated rolling average calculation blocks from all supervisors. The ATM now handles interval calculation internally via --sleep-interval-default parameter. - automation-tracking-manager.md: added sleep_interval_default to CREATE_TRACKING_ISSUE, added CYCLE_ANNOUNCEMENT_REVIEW operation (#11) - All 17 supervisor agents: replaced 7-line interval calc with --sleep-interval-default param - shared/tracking_discovery_guide.md: updated to reference ATM-handled interval |