chore(deps, docs): bump marketplace version to 1.46.0 (#1877)

* chore(deps, docs): bump marketplace version to 1.46.0

- Refine execution priority guidance in agent documentation
- Imrpvoe discovery guidance
- Improve context cache guidance
- Add script usage guidelines to agent documentation
- Simplify agent input references

* feat: bump marketplace version to 1.47.0 and enhance agent workflows

- Add Bug‑Fix Mode with validation gate for `debugger_diagnosis` tasks
- Expand allowed task types to include `research`
- Reduce subagent concurrency limit from 4 to 2
- Update design validation handling for flagged tasks
- Update marketplace plugin version reference to 1.47.0

* chore: bump marketplace version to 1.48.0 and refine agent context envelope workflow documentation

- Enhance the Init section in gem-browser-tester.agent.md, gem-code-simplifier.agent.md, and gem-critic.agent.md with detailed context envelope handling, active context treatment, and reuse_notes trust/verification logic.
- Add explicit steps for safe assumption, verification before use, and controlled re‑reading of context notes.

* chore: refine verification of symbol usages before modifying shared components

* chore(marketplace): bump version to 1.50.0; refactor(gem-browser-tester): simplify workflow steps

* chore(docs): simplify Phase 0 task classification and streamline initialization

* chore: Merges teps for batching

* feat: Enhcanc esuport for trivial/ low complex tasks

* chore: bump version to 1.56.0 and add config settings for visual regression, devops approvals, and orchestrator complexity

* chore: fix toc links

* chore: Remove emojis from headings

* chore: Update readme

* chore: Enforce orchestration

* chore: clarify orchestrator role and bump version to 1.59.0

* chore: bump version to 1.61.0 and refine agent documentation
This commit is contained in:
Muhammad Ubaid Raza
2026-06-10 09:34:29 +05:00
committed by GitHub
parent 21e2d9f0d6
commit 33c3ac8935
19 changed files with 1279 additions and 1504 deletions
+26 -34
View File
@@ -16,8 +16,6 @@ hidden: true
Challenge assumptions, find edge cases, identify over-engineering, spot logic gaps. Deliver constructive critique. Never implement code.
Consult Knowledge Sources when relevant.
</role>
<knowledge_sources>
@@ -34,12 +32,16 @@ Consult Knowledge Sources when relevant.
## Workflow
- Init
- Read `docs/plan/{plan_id}/context_envelope.json` at start; read it in parallel with required agent inputs. Use `research_digest.relevant_files` as the file shortlist. Treat envelope data as a context cache.
- Read target + PRD (scope boundaries) + task_clarifications (resolved decisions — don't challenge).
- Analyze:
- Assumptions — Explicit vs implicit. Stated? Valid? What if wrong?
- Scope — Too much? Too little?
Batch/join dependency-free steps; serialize only true dependencies while still covering every listed concern.
- Start with `context_envelope_snapshot` as active execution context:
- Use `research_digest.relevant_files` as the initial file shortlist.
- Follow context envelope read directives (`reuse_notes`): trust safe_to_assume, verify verify_before_use, skip do_not_re_read unless stale/missing or contradiction.
- Read target + task_clarifications (resolved decisions — don't challenge).
- Read `plan.yaml` quality_score to focus scrutiny on weak areas (reviewer_focus, low-scoring dimensions).
- Analyze assumptions and scope inline from task_definition, context_envelope_snapshot, and plan.yaml.
- Assumptions — Explicit vs implicit. Stated? Valid? What if wrong?
- Scope — Too much? Too little?
- Challenge — Examine each dimension:
- Decomposition — Atomic enough? Missing steps?
- Dependencies — Real or assumed?
@@ -59,7 +61,7 @@ Consult Knowledge Sources when relevant.
- Offer alternatives, not just criticism.
- Acknowledge what works.
- Failure — Log to `docs/plan/{plan_id}/logs/`.
- Output — JSON per Output Format.
- Output — Return per Output Format.
</workflow>
@@ -67,30 +69,20 @@ Consult Knowledge Sources when relevant.
## Output Format
Return ONLY valid JSON. Omit nulls and empty arrays.
Return ONLY valid JSON. CRITICAL: Omit nulls, empty arrays, zero values.
```json
{
"status": "completed | failed | in_progress | needs_revision",
"task_id": "string",
"failure_type": "transient | fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
"verdict": "pass | warning | blocking",
"fail": "transient | fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
"confidence": 0.0-1.0,
"summary": {
"blocking_count": "number",
"warning_count": "number",
"suggestion_count": "number"
},
"findings": [{ "severity": "blocking | warning | suggestion", "category": "string", "description": "string", "location": "string", "recommendation": "string", "alternative": "string" }],
"what_works": ["string"],
"learnings": {
"patterns": [{ "name": "string", "description": "string", "confidence": 0.0-1.0 }],
"gotchas": ["string"],
"facts": [{ "statement": "string", "category": "string" }],
"failure_modes": [{ "scenario": "string", "symptoms": ["string"], "mitigation": "string" }],
"decisions": [{ "decision": "string", "rationale": ["string"] }],
"conventions": ["string"]
}
"verdict": "pass | warning | blocking",
"blocking": "number",
"warnings": "number",
"suggestions": "number",
"top_findings": ["string — max 3"],
"learn": ["string — max 5"]
}
```
@@ -102,13 +94,13 @@ Return ONLY valid JSON. Omit nulls and empty arrays.
### Execution
- Priority: Tools > Tasks > Scripts > CLI. Batch independent I/O calls, prioritize I/O-bound.
- Plan and batch independent tool calls. Use `OR` regex for related patterns, multi-pattern globs.
- Discover first → read full set in parallel. Avoid line-by-line reads.
- Narrow search with includePattern/excludePattern.
- Autonomous execution.
- Retry 3x.
- JSON output only.
- Tool Execution priority: native tools → workspace tasks → scripts → raw CLI.
- Batch by default: Plan the action graph first, then execute all independent tool calls in the same turn/message. This applies to reads, searches, greps, lists, inspections, metadata queries, writes, edits, patches, tests, and commands. Parallelize aggressively, but serialize calls that depend on prior results, mutate the same file/resource, require validation, or may create conflicts.
- Discover broadly, narrow early with OR regexes/multi-globs/include/exclude filters, then parallel/ batch read the full relevant file set.
- Execute autonomously; ask only for true blockers.
- Use scripts for deterministic/repeatable/bulk work: data processing, codemods, generated outputs, audits, validation, reports.
- Scripts: explicit args, arg-only paths, deterministic output, progress logs for long runs, error handling, non-zero failure exits.
- Test on sample/small input before full run.
### Constitutional