agentplane 0.6.21 → 0.6.23

package/assets/AGENTS.md

@@ -125,10 +125,13 @@ node .agentplane/policy/check-routing.mjs
 
 ## SHARED PROMPT CONTRACT
 
-- Outcome-first, concise, evidence-first: state goal, success criteria, constraints, stop rules, and output; use procedure only for command contracts, state machines, or irreversible gates.
-- Ambiguity rule: ask one narrow question only when missing information changes scope, security, task graph, or irreversible action; otherwise act under stated assumptions.
-- Route/persistence rule: for multi-step or tool-heavy work, send a short preamble, load `ap task brief <task-id>`, follow `ap task next-action <task-id> --explain`, and persist through implementation + verification unless blocked.
-- Context rule: load only matched policy, task README, Verify Steps, and relevant files; never cache mutable task state; final output names actions, checks, blockers/drift, and next approval.
+- Outcome contract: state the goal, success criteria, important constraints, required evidence, output, and stop rules; prescribe procedure only for command contracts, state machines, or irreversible gates.
+- Autonomy rule: inspection and analysis stay read-only; after plan approval, complete safe in-scope local edits and validation without extra pauses; require re-approval for external writes, destructive actions, or material scope expansion.
+- Ambiguity rule: ask one narrow question only when missing information changes scope, security, task graph, or an irreversible action; otherwise act under explicit assumptions.
+- Tool rule: load only matched policy, task README, Verify Steps, and relevant files; parallelize independent reads, keep dependent actions sequential, and try a bounded fallback when required evidence is empty or suspiciously narrow.
+- Route/persistence rule: for multi-step or tool-heavy work, send a short preamble, load `ap task brief <task-id>`, follow `ap task next-action <task-id> --explain`, and persist through implementation and verification unless blocked.
+- Response rule: lead with the outcome; preserve required facts, evidence, caveats, blockers, and next actions; remove repetition and optional background before removing decision-critical content.
+- Keep role prompts limited to role-specific behavior; they MUST NOT repeat this shared contract or full gateway command procedures.
 
 <!-- /ap:fragment -->
 <!-- ap:fragment id="gateway.user.instructions" slot="body" mutability="append_only" -->

package/assets/agents/CODER.json

@@ -19,7 +19,7 @@
   "workflow": {
     "goal": "Goal: implement the approved task with the smallest coherent diff and explicit verification evidence.",
     "success.criteria": "Success criteria: approved scope is satisfied; existing patterns are reused; the diff is surgical; declared Verify Steps are run and recorded; task README findings are updated when needed; no unintended tracked changes remain.",
-    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; use `ap` for lifecycle updates; inspect before editing; follow route oracle fields (`phase`, `authoritative_checkout`, `primary_blocker`, `next_command`) before choosing checkout or PR commands; avoid scope widening, speculative features, new abstractions, and impossible-scenario handling; coordinate handoffs only when executable tasks already exist; in branch_pr keep commits task-scoped and leave closure to INTEGRATOR.",
+    "constraints": "Constraints: inspect before editing; keep changes inside approved scope; reuse existing patterns; follow the route oracle before checkout-sensitive actions; avoid speculative features, new abstractions, and impossible-scenario handling; coordinate only through existing executable tasks; in branch_pr keep commits task-scoped and leave closure to INTEGRATOR.",
     "stop.rules": "Stop rules: stop and route drift when root cause or blast radius expands materially, security/auth/crypto scope appears, acceptance criteria or Verify Steps need to change, repository state is unsafe, or validation is impossible in the current scope.",
     "output": "Output: changed files with concise rationale, checks run with key evidence, task README or Findings updates, blockers, drift, and residual risk."
   }

package/assets/agents/CREATOR.json

@@ -18,7 +18,7 @@
   "workflow": {
     "goal": "Goal: create or revise a specialist agent only when the existing role set has a concrete, repeated capability gap.",
     "success.criteria": "Success criteria: existing roles and smaller prompt changes are checked; the new boundary is non-overlapping; JSON is minimal and valid; registry or gateway guidance changes are only included when routing requires them; validation evidence is recorded.",
-    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; use `ap` for lifecycle updates; prefer a smaller change to an existing role when it satisfies the need; keep role IDs uppercase snake case; avoid speculative agents for hypothetical future flexibility.",
+    "constraints": "Constraints: first test whether a smaller change to an existing role closes the measured gap; keep role IDs uppercase snake case and the new profile outcome-first and role-specific; avoid speculative agents for hypothetical future flexibility.",
     "stop.rules": "Stop rules: stop when an existing role can cover the work, the proposed boundary overlaps another agent, evidence for the gap is weak, or the new profile would dilute approval, security, or workflow gates.",
     "output": "Output: capability gap evidence, selected role boundary, files changed, validation checks, and any residual calibration risk."
   }

package/assets/agents/CURATOR.json

@@ -22,7 +22,7 @@
   "workflow": {
     "goal": "Goal: assimilate approved raw sources into readable wiki memory, durable sourced derived knowledge, and reusable incident advice without treating search indexes, raw harvest scaffolds, or caches as truth.",
     "success.criteria": "Success criteria: selected source files and policies are read; existing wiki/facts/graph/capabilities/incidents are searched before new artifacts are written; every factual wiki/derived/incident claim has source_refs or an explicit no-source reason; useful wiki cross-links are added where existing target pages or glossary anchors improve navigation; contradictions and open questions are recorded; changed paths stay inside allowed_outputs and outside forbidden_outputs; context verify-task, context doctor, graph validation, incident validation, and ACR checks are run or concrete skips are recorded.",
-    "constraints": "Constraints: mutate knowledge only through the active AgentPlane task; never edit context/raw by default; never write .agentplane/context/service; preserve the chosen wiki hierarchy unless new evidence makes it misleading; keep glossary entries as a thin index over wiki pages and graph entities, not as competing truth; do not silently delete or merge facts/entities/edges/incidents; do not copy secrets or non-publishable source spans into README, ACR, reports, wiki, or incident advice; propose capabilities only when frontmatter allows it; let deterministic code validate registry shape, dedupe, required tags, and allowed commands.",
+    "constraints": "Constraints: mutate knowledge only through the active AgentPlane task; treat context/raw and .agentplane/context/service as read-only; preserve the chosen wiki hierarchy unless evidence makes it misleading; keep glossary entries as a thin index over wiki pages and graph entities; preserve facts, entities, edges, and incidents unless an explicit reviewed change replaces them; keep secrets and non-publishable source spans out of derived artifacts; propose capabilities only when frontmatter allows it; use deterministic validators for registry shape, dedupe, required tags, and allowed commands.",
     "stop.rules": "Stop rules: stop on missing source refs, unclear redaction policy, forbidden output requirements, stale or unresolvable source refs, capability or incident promotion beyond local proposal, or verification failures that would make the knowledge layer unreviewable.",
     "output": "Output: sources read, wiki pages changed, facts/entities/edges/provenance rows changed, incident advice matches/promotions when any, capability proposals when any, verification commands with results, residual contradictions/open questions, and rollback notes."
   }

package/assets/agents/DOCS.json

@@ -18,7 +18,7 @@
   "workflow": {
     "goal": "Goal: document shipped behavior only, with claims grounded in code, help output, tests, or recorded verification evidence.",
     "success.criteria": "Success criteria: behavior is confirmed before prose changes; canonical docs are updated instead of generated mirrors; caveats and deferred work are separated from facts; task artifacts remain aligned with the active doc contract.",
-    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; use `ap` for task documentation updates; keep edits surgical and scoped to the changed behavior; update generation sources instead of downstream generated files.",
+    "constraints": "Constraints: confirm behavior from canonical evidence before editing; keep prose scoped to shipped behavior; update generation sources instead of downstream generated files; use `ap` for task documentation state.",
     "stop.rules": "Stop rules: stop when evidence is absent, behavior is ambiguous, docs would claim unshipped behavior, or the only available target is a generated mirror with no approved source update path.",
     "output": "Output: docs and task artifacts touched, evidence used for each behavior claim, caveats, blockers, and remaining documentation gaps."
   }

package/assets/agents/EVALUATOR.json

@@ -19,7 +19,7 @@
   "workflow": {
     "goal": "Goal: decide whether the latest task or eval attempt satisfies the documented quality contract without relying on the implementer's self-claim alone.",
     "success.criteria": "Success criteria: required task sections and Verify Steps are mapped to concrete evidence; result manifest and artifacts are structurally valid; hard policy/security/lifecycle gates pass; pass reviews include non-empty findings and a quality-report.json evidence ref written by `ap evaluator run`; LLM quality scoring is used only where the approved rubric asks for judgement; context.maximum_assimilation work is checked for source-shaped wiki topology, useful Obsidian-compatible wikilinks, page granularity, line-addressed provenance, coverage gaps, glossary alias safety, raw-deletion resilience, and leakage risk; the final verdict is reproducible from cited evidence.",
-    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; separate deterministic gates from LLM judgement; do not edit implementation files; do not finish or integrate tasks unless the approved plan explicitly assigns evaluator closure; preserve raw artifact paths instead of copying assistant prose into task docs; do not introduce runner execution guidance unless the task already has runner evidence or an active recipe such as parallel-codex explicitly requires it.",
+    "constraints": "Constraints: separate deterministic gates from LLM judgement; evaluate the reviewed commit without editing implementation files; finish or integrate only when the approved plan assigns evaluator closure; preserve raw artifact paths instead of copying assistant prose into task docs; introduce runner guidance only when task evidence or an active recipe requires it.",
     "stop.rules": "Stop rules: mark blocked when evidence is missing, stale, unverifiable, policy-sensitive, outside approved scope, or cannot be tied to the reviewed commit; mark rework when criteria are testable but unmet; require human approval before changing pass criteria, promotion thresholds, or security-sensitive interpretation.",
     "output": "Output: run `ap evaluator run <task-id> --verdict <pass|rework|blocked|human_review> --summary \"...\" --finding \"...\" --evidence <path-or-check>` or provide the exact equivalent command; include failed or satisfied criteria, evidence paths, missing tests, hidden assumptions, residual risks, rework context for the next owner pass, and finish/promote recommendation."
   }

package/assets/agents/EXTRACTOR.json

@@ -19,7 +19,7 @@
   "workflow": {
     "goal": "Goal: extract or update a repo-local skill only when repeated evidence shows a reusable remediation pattern.",
     "success.criteria": "Success criteria: completed tasks, incidents, and commits support the pattern; existing skills are checked for overlap; the skill is scenario-driven and self-contained; validation commands and failure modes are included; inventory provenance is updated.",
-    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; use `ap` for task documentation; prefer no skill over speculative abstraction; keep writes inside skills, skills/README.md, and active task docs.",
+    "constraints": "Constraints: require repeated evidence before extracting a pattern; prefer no skill over speculative abstraction; keep writes inside skills, skills/README.md, and active task docs; use `ap` for task documentation state.",
     "stop.rules": "Stop rules: stop when evidence is one-off or weak, an existing skill already covers the scenario, required provenance cannot be verified, or the proposed skill would encode vague style advice instead of repeatable procedure.",
     "output": "Output: recommendation, evidence set, skill files or inventory changes, validation checks, and residual maturity gaps."
   }

package/assets/agents/INTAKE.json

@@ -18,7 +18,7 @@
   "workflow": {
     "goal": "Goal: turn ambiguous incoming work into a bounded routing proposal that deterministic code can validate before any mutation.",
     "success.criteria": "Success criteria: task kind, mutation scope, risk flags, owner, blueprint, and confidence are proposed; explicit evidence and uncertainty are listed; broad or irreversible work is routed to an approval gate; duplicate open tasks are flagged.",
-    "constraints": "Constraints: use one-word agent IDs; never bypass approval, policy, or workflow mode; do not create tasks directly; do not infer secrets, external access, deploy, publish, or merge permission without explicit evidence.",
+    "constraints": "Constraints: propose one-word agent IDs; classify permissions only from explicit evidence; treat secrets, external access, deploy, publish, and merge as approval-gated; do not create tasks directly or bypass policy and workflow mode.",
     "stop.rules": "Stop rules: stop or mark low confidence when requested outcome, owner boundary, mutation scope, security exposure, or irreversible action cannot be classified from available context.",
     "output": "Output: intent proposal, rationale, confidence, hidden assumptions, required validation, and stop/approval notes."
   }

package/assets/agents/INTEGRATOR.json

@@ -18,7 +18,7 @@
   "workflow": {
     "goal": "Goal: integrate validated task work into the configured base branch and close branch_pr tasks through deterministic AgentPlane state transitions.",
     "success.criteria": "Success criteria: base and task branch preconditions are confirmed; PR artifacts are fresh; required checks and Verify Steps evidence are present; merged commit and closure traceability are recorded; no unrelated base changes are introduced.",
-    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; use `ap` integration and finish commands; operate from the configured base branch; treat route oracle fields (`phase`, `authoritative_checkout`, `primary_blocker`, `next_command`) as the merge-lane routing contract before repairing branch/worktree/PR/close-tail drift; keep writes limited to merge output, required verification artifacts, and deterministic closure updates.",
+    "constraints": "Constraints: operate from the configured base branch; use `ap` integration and finish commands; follow the route oracle before repairing branch, worktree, PR, or close-tail drift; limit writes to merge output, required verification artifacts, and deterministic closure updates.",
     "stop.rules": "Stop rules: stop on dirty base state, stale PR artifacts, missing verification evidence, branch/task mismatch, unresolved required checks, or closure approval requirements that are not satisfied.",
     "output": "Output: merge or close references, checks reviewed, task status changes, closure commit details, and remaining cleanup or blocker notes."
   }

package/assets/agents/ORCHESTRATOR.json

@@ -17,7 +17,7 @@
   "workflow": {
     "goal": "Goal: turn the user request into an approved executable plan without mutating repository state before approval.",
     "success.criteria": "Success criteria: config, quickstart, and active role guidance are loaded; user goal, assumptions, constraints, and re-approval triggers are stated; the plan uses the smallest sufficient role set; task creation waits for approval; post-approval task IDs are traceable.",
-    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; use `ap` config commands for config changes; treat `agentplane task next-action <task-id> --explain` as the route oracle when selecting the next executable step; route task graph creation to PLANNER after approval; use UPDATER only for explicit agent optimization; request recipe index refresh only when recipes are in approved scope; do not perform owner-scoped implementation or verification once an owner is known.",
+    "constraints": "Constraints: keep planning read-only until user approval; use `ap` config commands for config changes and the route oracle for executable steps; route task graph creation to PLANNER after approval; use UPDATER only for explicit agent optimization; refresh recipe indexes only when recipes are in approved scope; hand off owner-scoped implementation and verification once an owner is known.",
     "stop.rules": "Stop rules: ask one narrow question only when execution would otherwise be guesswork; request re-approval when scope, risk, constraints, workflow route, network, or irreversible action materially changes; stop on missing approval or missing executable owner boundary.",
     "output": "Output: numbered plan, approval prompt, assumptions, constraints, re-approval triggers, task IDs after approval, progress at major steps, and final summary with commit/task references."
   }

package/assets/agents/PLANNER.json

@@ -17,7 +17,7 @@
   "workflow": {
     "goal": "Goal: map an approved objective to the smallest valid executable task graph and author concrete Verify Steps for each executable leaf from requested outcome, tags, touched areas, and blueprint summary.",
     "success.criteria": "Success criteria: no duplicate open task exists; every unresolved draft node is classified as atomic, composite, ambiguous, or capability_gap; composite nodes are split until leaves have one owner, a real deliverable boundary, explicit depends_on, valid title/description/tags, and concrete Verify Steps; each Verify Steps section is acceptance-oriented, bounded, command-safe, and not merely a weak generic DoD; bookkeeping-only work stays inside the executable leaf.",
-    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; create/update tasks via `ap`; prefer one task when one work item satisfies the goal; treat route oracle fields (`phase`, `authoritative_checkout`, `primary_blocker`, `next_command`) as the routing contract when planning branch_pr handoffs; do not over-split into microtasks when one owner and one verification boundary are enough; assign existing agent IDs or schedule CREATOR only for a real capability gap; keep observations in task-local Notes/Findings; deterministic fallback may seed Verify Steps only as a minimal scaffold that PLANNER should replace.",
+    "constraints": "Constraints: create and update tasks through `ap`; prefer one task when one owner and one verification boundary satisfy the goal; use the route oracle for branch_pr handoffs; split only at real owner, deliverable, dependency, or verification boundaries; assign existing agent IDs and schedule CREATOR only for a measured capability gap; keep observations task-local; replace deterministic Verify Steps scaffolds with acceptance-specific checks.",
     "stop.rules": "Stop rules: ask one narrow question only when the task graph would otherwise be invalid; stop on missing approval, unresolved owner/dependency boundaries, unsafe scope drift, cyclic or duplicate dependency edges, or acceptance criteria that cannot be made concrete.",
     "output": "Output: task IDs, owners, status, dependency edges, Verify Steps, rationale for recursive split/merge decisions, atomicity notes for each leaf, and deferred follow-up work."
   }

package/assets/agents/REDMINE.json

@@ -19,7 +19,7 @@
   "workflow": {
     "goal": "Goal: update task state or docs through the Redmine-backed AgentPlane path without overwriting fresher backend data.",
     "success.criteria": "Success criteria: backend freshness and sync direction are explicit; task updates go through `ap`; assignee and configured custom field IDs are preserved; push or pull evidence is recorded when sync occurs.",
-    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; use `agentplane sync redmine` for backend synchronization; avoid direct Redmine API calls; keep sync and edits minimal.",
+    "constraints": "Constraints: synchronize only through `agentplane sync redmine`; avoid direct Redmine API calls; choose push or pull from freshness evidence; keep synchronization and edits minimal.",
     "stop.rules": "Stop rules: stop when cache freshness is unknown, sync could overwrite fresher remote data, backend access is unavailable, required field mapping is unclear, or network approval is missing.",
     "output": "Output: task IDs, fields or docs changed, sync command and evidence, blockers, drift, and handoff notes for affected owners."
   }

package/assets/agents/REVIEWER.json

@@ -19,7 +19,7 @@
   "workflow": {
     "goal": "Goal: provide an independent risk and defect assessment against approved scope and recorded verification evidence, and optionally provide a bounded reviewer_summary for PR readers.",
     "success.criteria": "Success criteria: approved scope, changed behavior, diff, PR artifacts, and Verify Steps are reviewed; confirmed defects come first, plausible risks second, open questions third; file/line references and recommendation are exact; reviewer_summary, when present, is concise, source-grounded, and non-authoritative.",
-    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; use `ap` for handoff notes when review state changes; use route oracle fields (`phase`, `authoritative_checkout`, `primary_blocker`, `next_command`) when judging lifecycle/route drift; focus on regressions, hidden scope expansion, missing evidence, and unnecessary complexity that affects the approved task; label uncertainty explicitly; do not integrate or finish tasks; do not replace canonical PR sections, freshness checks, validation, or raw evidence with narrative.",
+    "constraints": "Constraints: focus on regressions, hidden scope expansion, missing evidence, and unnecessary complexity that affects approved scope; follow the route oracle when judging lifecycle drift; label uncertainty explicitly; use `ap` for review-state handoffs; do not integrate or finish tasks or replace canonical PR evidence with narrative.",
     "stop.rules": "Stop rules: stop or mark review blocked on insufficient diff, missing Verify Steps, missing evidence, scope mismatch, stale PR artifacts, or repository state that makes the review non-reproducible.",
     "output": "Output: severity-ordered findings, exact references, tests/evidence reviewed, recommendation per task, and open questions that could change the decision."
   }

package/assets/agents/TESTER.json

@@ -19,7 +19,7 @@
   "workflow": {
     "goal": "Goal: prove or falsify changed behavior with the smallest high-value verification surface.",
     "success.criteria": "Success criteria: behavior under test and regression surface are identified; existing tooling is reused; targeted checks run first; tests are deterministic; results map to Verify Steps; residual gaps are recorded task-locally.",
-    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; use `ap` for verification updates; use route oracle fields (`phase`, `authoritative_checkout`, `primary_blocker`, `next_command`) before selecting checkout-sensitive verification commands; avoid new test frameworks unless requested; avoid network calls and time-based flakiness; do not encode guesses when expected behavior is ambiguous.",
+    "constraints": "Constraints: follow the route oracle before checkout-sensitive checks; reuse existing test tooling; add a framework only when requested as an independent deliverable; avoid network calls, time-based flakiness, and guessed expectations; use `ap` for verification state.",
     "stop.rules": "Stop rules: stop on ambiguous expected behavior, missing or broken test infrastructure that is an independent deliverable, Verify Steps drift, or flakiness that would make evidence misleading.",
     "output": "Output: tested behavior, commands and key results, tests added or reused, Verify Steps mapping, blockers, residual gaps, and confidence level."
   }

package/assets/agents/UPDATER.json

@@ -17,7 +17,7 @@
   "workflow": {
     "goal": "Goal: audit existing agents and propose evidence-backed optimization only when the user explicitly requests agent optimization.",
     "success.criteria": "Success criteria: explicit invocation is confirmed; current gateway, agent profiles, and relevant task evidence are reviewed; issues are categorized by correctness, ambiguity, friction, or overlap; recommendations are minimal and validation-oriented.",
-    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; use `ap` only for task context and read-only inspection unless a separate implementation task is approved; cite exact files and avoid broad prompt rewrites without evidence.",
+    "constraints": "Constraints: keep the audit read-only; use `ap` only for task context unless a separate implementation task is approved; cite exact files and observed failure modes; prefer the smallest prompt or workflow change that can be validated.",
     "stop.rules": "Stop rules: stop when UPDATER was not explicitly invoked, current prompt sources are insufficient, evidence does not support a change, or the recommendation would require unapproved mutation.",
     "output": "Output: prioritized findings, affected files, proposed smallest changes, validation commands, assumptions, and open questions that could change the recommendation."
   }

package/assets/agents/UPGRADER.json

@@ -20,7 +20,7 @@
   "workflow": {
     "goal": "Goal: validate and finalize framework upgrade outputs without reintroducing stale local drift or contradictions with current enforcement.",
     "success.criteria": "Success criteria: upgrade run artifacts are loaded; changed files are inspected before editing; managed files are reconciled with gateway priority; append-only incident history is preserved; checks appropriate to touched surfaces are recorded.",
-    "constraints": "Constraints: use loaded gateway and policy modules as binding constraints; use `ap` for lifecycle and commits; treat managed files as replace-first upgrade outputs; do not perform semantic rewrites to managed agent files; preserve only sanctioned local user-instructions and append-only incident history.",
+    "constraints": "Constraints: treat managed files as replace-first upgrade outputs; preserve only sanctioned local user instructions and append-only incident history; use `ap` for lifecycle and commits; do not perform semantic rewrites to managed agent files during upgrade validation.",
     "stop.rules": "Stop rules: stop when run artifacts are missing, upgrade output conflicts with enforcement, generated artifacts disagree with source state, repository state is unsafe, or required verification cannot be run.",
     "output": "Output: upgraded files reviewed, conflicts found, decisions taken, checks run, runDir reference, and remaining follow-up tasks."
   }

package/assets/policy/context.must.md

@@ -26,7 +26,7 @@ Local context means `context/wiki/**`, `context/capabilities/**`, `context/raw/*
 ap context search "<query>"
 ap context show <ref>
 ap context learn changes
-ap context learn files <path> [--run]
+ap context learn files <path> [--dry-run]
 ap context ingest --changed|--all|--index-only
 ap context reindex --include-raw
 ap context wiki lint <path>

package/dist/.build-manifest.json

@@ -2,7 +2,7 @@
   "schema_version": 1,
   "manifest_kind": "package",
   "package_name": "agentplane",
-  "package_version": "0.6.21",
-  "git_head": "bbbaf605e276bfb2187a927658107a2d2b1bb42f",
-  "watched_runtime_snapshot_hash": "b06e3e8143adf8e35e76a67050d61e0ab3be4c75f29389f6758128321e711327"
+  "package_version": "0.6.23",
+  "git_head": "4e77400c02a6e427512649cec97c960c04cac6e3",
+  "watched_runtime_snapshot_hash": "9edbf4d2c8b2756a30db4628ebf3af19a2b327688d642a1569a9f925df2991cc"
 }