Skip to content

docs(readme,getting-started,commands): surface refinement/triage workflow + webinstaller alternative (#979, #984)#995

Merged
MScottAdams merged 3 commits into
masterfrom
agent4/docs/979-984-readme-refinement-webinstaller
May 8, 2026
Merged

docs(readme,getting-started,commands): surface refinement/triage workflow + webinstaller alternative (#979, #984)#995
MScottAdams merged 3 commits into
masterfrom
agent4/docs/979-984-readme-refinement-webinstaller

Conversation

@MScottAdams
Copy link
Copy Markdown
Collaborator

@MScottAdams MScottAdams commented May 8, 2026

Summary

Pair of adoption-blocker docs touches landing in one PR (#979 + #984). All changes are pure docs -- no script, task, schema, or behavior changes; skills/deft-directive-refinement/SKILL.md (the canonical agent-facing source of truth) intentionally untouched.

Closes

Changes

README.md -- two new subsections under the Getting Started area:

docs/getting-started.md (#979) -- new ## Working an existing backlog section covering:

  • Scoped first populate flag surface (--limit / --state / --batch-size / --delay-ms / --repo).
  • The canonical Phase 0 numbered action menu (accept | reject | defer | needs-ac | mark-duplicate plus Discuss / Back).
  • The three-tier inventory model in user vocabulary (cache .deft-cache/github-issue/ -> audit log vbrief/.eval/candidates.jsonl -> accepted backlog vbrief/proposed/).
  • The rule that writes flow only through task triage:accept (which delegates to task issue:ingest).
  • Why this avoids the shared GraphQL bucket drain (REST-backed cache, batched delays, automatic 429 retries via upstream Retry-After, no live gh issue view per decision).

commands.md (#979) -- new ## Backlog triage & cache tasks section surfacing every task triage:* and task cache:* verb with verb-to-outcome descriptions (bootstrap / accept / reject / defer / needs-ac / mark-duplicate / bulk-* / refresh-active / status / history / reset; cache fetch-all / get / invalidate / prune); cross-links back to the getting-started walkthrough.

Vocabulary parity -- all three doc surfaces use vocabulary identical to skills/deft-directive-refinement/SKILL.md Phase 0 so there is no drift between agent-facing and user-facing copy.

vBRIEF lifecycle

  • vbrief/pending/2026-05-08-979-...vbrief.json -> vbrief/active/ (status: running) via task vbrief:activate
  • vbrief/pending/2026-05-08-984-...vbrief.json -> vbrief/active/ (status: running) via task vbrief:activate

Both vBRIEFs will lifecycle-move to vbrief/completed/ via task scope:complete after Greptile review-cycle exits clean.

Validation

  • task check green (4389 passed, 3 skipped, 1 xfailed; 942 files clean per verify:encoding).
  • task pr:check-closing-keywords -- --commits-file <commit messages> clean (no closing-keyword negation/quotation/example/code-block hits).

PR Checklist

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented May 8, 2026

Greptile Summary

This is a pure-docs PR that closes two adoption-blocker issues: it surfaces the Phase 0 triage/refinement workflow to end users across three coordinated doc surfaces, and adds the hosted webinstaller at webinstaller.fly.dev as a visible alternative installer path in README.md.

  • README.md gains two new subsections: an Alternative installer callout for the hosted webinstaller (with trade-off note) and a ### 5. Backlog triage subsection with trigger words, the scoped bootstrap command, and cross-links to the full walkthrough.
  • docs/getting-started.md gains a ## Working an existing backlog section covering the flag surface, the numbered action menu, the three-tier inventory model (cache → audit log → accepted backlog), and the REST-backed rationale for avoiding the GraphQL bucket drain.
  • commands.md gains a ## Backlog triage & cache tasks section documenting every task triage:* and task cache:* verb; the triage:refresh-active entry was updated from the prior draft to correctly reference gh api repos/<owner>/<repo>/issues/<N> instead of gh issue view --json, addressing the concern raised in review.

Confidence Score: 5/5

Pure documentation change with no script, task, schema, or behavior modifications — safe to merge.

All changed files are Markdown or JSON lifecycle metadata. The three doc surfaces are internally consistent, vocabulary aligns with the canonical skills/deft-directive-refinement/SKILL.md Phase 0, and the triage:refresh-active REST-path concern from the prior review cycle was addressed in this diff. No logic, schema, or executable code was touched.

CHANGELOG.md — a duplicate, truncated gh_rest.py stub was introduced in this diff (noted in a prior review thread); that entry should be cleaned up before the next release cut.

Important Files Changed

Filename Overview
docs/getting-started.md Adds comprehensive ## Working an existing backlog section with four numbered steps covering the flag surface, action menu, three-tier inventory model, and GraphQL avoidance rationale. Vocabulary and REST-path references are consistent with the updated commands.md.
commands.md Adds ## Backlog triage & cache tasks section documenting all task triage:* and task cache:* verbs. Notably, triage:refresh-active now correctly cites gh api repos/<owner>/<repo>/issues/<N> and explicitly notes the preference over gh issue view --json, addressing the concern from the prior review thread.
README.md Adds alternative installer callout and ### 5. Backlog triage subsection. Content is accurate; trigger words "triage" / "work the cache" / "pre-ingest" are surfaced here but the AGENTS.md Skill Routing table (noted in prior review thread) does not yet map them to the refinement skill.
CHANGELOG.md Adds a combined entry for #979 and #984. A duplicate, truncated stub for feat(scripts): gh_rest.py was introduced (unclosed bold markup, missing description body) — this was flagged in the prior review thread and remains unresolved in this diff.
vbrief/completed/2026-05-08-979-docs-surface-refinementtriage-workflow-to-end-users-phase-0.vbrief.json Status lifecycle move from pendingcompleted; updated timestamp added to vBRIEFInfo and plan blocks. No issues.
vbrief/completed/2026-05-08-984-docsreadme-call-out-httpswebinstallerflydev-as-an-alternativ.vbrief.json Status lifecycle move from pendingcompleted; updated timestamps added. No issues.

Reviews (4): Last reviewed commit: "chore(vbrief): lifecycle-move #979 + #98..." | Re-trigger Greptile

Comment thread CHANGELOG.md
Comment thread commands.md Outdated
Comment thread README.md
Copy link
Copy Markdown

@deft-slizard deft-slizard Bot left a comment

Choose a reason for hiding this comment

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

SLizard Review — 0 findings across 6 file(s) · confidence 0.29

Unable to provide confident assessment at current analytical confidence (0.29). Manual review recommended.

Files reviewed:

  • CHANGELOG.md
  • README.md
  • commands.md
  • docs/getting-started.md
  • vbrief/active/2026-05-08-979-docs-surface-refinementtriage-workflow-to-end-users-phase-0.vbrief.json
  • vbrief/active/2026-05-08-984-docsreadme-call-out-httpswebinstallerflydev-as-an-alternativ.vbrief.json

⚠️ Confidence gap: This review produced 0 findings at confidence 0.29 (below 0.60). No clean-review rationale was captured — the reviewer cannot confirm whether the clean result reflects genuine absence of issues or insufficient analytical confidence. Manual review is recommended.

Deterministic checks: passed — vBRIEF traceability checks passed.

Review coverage

  • Reviewed files: CHANGELOG.md, README.md, commands.md, docs/getting-started.md, vbrief/active/2026-05-08-979-docs-surface-refinementtriage-workflow-to-end-users-phase-0.vbrief.json, vbrief/active/2026-05-08-984-docsreadme-call-out-httpswebinstallerflydev-as-an-alternativ.vbrief.json
  • Skipped files: none
  • Source: github @ c34929ae1a11

Context used

  • Static findings: 2
  • Static tools: diff-truncation-check
  • Graph/blast radius: 0 changed node(s), 0 affected node(s)
  • Vector context chunks: 21
  • Context availability: full
  • Review categories: default
  • Deterministic checks: vbrief-traceability=passed, markdown-fences=passed, unused-exports=passed, query-docstring=passed, xss-sprintf=passed, markdown-xref=passed, aria-target=passed, semantic-role=passed, aria-containment=passed, redundant-assertion=passed, resource-lifecycle=passed, cross-diff-consistency=passed, redundant-css-block=passed, template-placeholder=passed, void-async-signal=passed, spread-override=passed, json-indent-consistency=passed, dep-swap=passed, powershell-scoping=passed, diff-truncation=failed, exception-type-contract=passed, dead-none-guard=passed, access-declaration=passed, unused-option=passed, css-property-interaction=passed, jsx-style-indent=passed, regex-breadth=passed, cartesian-fan-out=passed, exec-stdout-parse=passed, sentinel-error-wiring=passed, hardcoded-filemode=passed, api-response-shape=passed, python-cli-arg=passed, taskfile-namespace=passed, vbrief-schema=passed, go-shell-injection=passed, go-discarded-error=passed, inline-style-proliferation=passed, unnecessary-nonnull-assertion=passed, ssrf-guard-completeness=passed, error-message-leak=passed, puppeteer-resource-cap=passed, trivial-argument=passed, dead-store=passed, phantom-import=passed, fetch-timeout-guard=passed, log-level-expected-path=passed, unified-diff-construction=passed, graph-incompleteness=passed, lockfile-version-suppression=passed
  • Degraded context: Decision capped at comment: deterministic check(s) failed (diff-truncation) (issue #458).

Suggested verification

  • (agent) Spot-check the highest-risk changed files and confirm the clean review did not skip relevant files or context.
  • (static) Review 2 deterministic/static finding(s) included in the evidence set.

Agent verification brief

  • PR/CR: deftai/directive#995
  • Head SHA: c34929ae1a11a0f61c7e4e76971b7a536af67555
  • Decision: comment
  • Highest-risk claims: none
  • Reviewed files: CHANGELOG.md, README.md, commands.md, docs/getting-started.md, vbrief/active/2026-05-08-979-docs-surface-refinementtriage-workflow-to-end-users-phase-0.vbrief.json, vbrief/active/2026-05-08-984-docsreadme-call-out-httpswebinstallerflydev-as-an-alternativ.vbrief.json
  • Skipped files: none
  • Evidence sources: static analysis, call graph/blast radius, vector context, deterministic checks
  • Known blind spots: Decision capped at comment: deterministic check(s) failed (diff-truncation) (issue #458).

Decision: comment
Merge impact: non-blocking
Review confidence: 0.29
Decision confidence: 0.29
Finding confidence: n/a
Reason: Findings are advisory under the current severity/confidence policy.
Important files: 6 changed file(s) reviewed; no finding hotspots identified.
Review scope: 6 files, 107 additions, 5 deletions

slizard v0.3.206

MScottAdams added a commit that referenced this pull request May 8, 2026
 review-clean)

Greptile re-review on PR #995 confidence 5/5, no P0/P1 findings, last reviewed commit matches HEAD. Both scope vBRIEFs lifecycle-move via task scope:complete:
- 2026-05-08-979 (docs: surface refinement/triage workflow)
- 2026-05-08-984 (docs(readme): webinstaller alternative installer)

Follow-up #1000 filed for the AGENTS.md trigger-words gap (P2 from same Greptile pass; AGENTS.md owned by another agent in this cohort).
…flow + webinstaller alternative (#979, #984)

- README: new Backlog triage subsection (trigger words, scoped first-run command, GraphQL bucket cross-reference, links into docs/getting-started.md and commands.md).
- README: new Alternative installer callout linking https://webinstaller.fly.dev/ next to (not below) the existing primary install instructions; webinstaller stays an alternative path, NOT the default.
- docs/getting-started.md: new Working an existing backlog section (scoped first populate flag surface, Phase 0 numbered action menu, three-tier model in user vocabulary, REST-backed-cache rationale).
- commands.md: new Backlog triage and cache tasks section surfacing every task triage:* and task cache:* verb with verb-to-outcome descriptions; cross-links back to the getting-started walkthrough.
- All three doc surfaces use vocabulary identical to skills/deft-directive-refinement/SKILL.md Phase 0 (no agent-vs-user drift).
- CHANGELOG.md: combined [Unreleased] entry under ### Added.
- vBRIEF lifecycle: 2026-05-08-979 and 2026-05-08-984 promoted pending/ -> active/ via task vbrief:activate.

Closes #979
Closes #984
- CHANGELOG.md: restore truncated eat(scripts): gh_rest.py (#961) entry that was accidentally clipped to a bare heading by the prior insertion. Restored verbatim from master:CHANGELOG.md so the full description (seven REST helpers, GhRestError, UTF-8 payload safety, 63 tests, known limitations) is preserved in the release record.
- commands.md (#979): rephrase 	ask triage:refresh-active description -- replace gh issue view --json updatedAt (GraphQL) with gh api repos/<owner>/<repo>/issues/<N> (REST) per AGENTS.md Multi-agent orchestration discipline REST-over-GraphQL rule. Description now also explicitly cross-references the rule so the user-facing doc does not contradict the framework rule.

Greptile finding 3 (README trigger words not wired into AGENTS.md Skill Routing) is a P2 follow-up: AGENTS.md is owned by another agent in this cohort (per dispatch-envelope CONSTRAINTS) and the trigger words ARE listed inside skills/deft-directive-refinement/SKILL.md 	riggers: frontmatter and Session Model. Filing a separate GitHub issue to track the AGENTS.md routing-table addition.
 review-clean)

Greptile re-review on PR #995 confidence 5/5, no P0/P1 findings, last reviewed commit matches HEAD. Both scope vBRIEFs lifecycle-move via task scope:complete:
- 2026-05-08-979 (docs: surface refinement/triage workflow)
- 2026-05-08-984 (docs(readme): webinstaller alternative installer)

Follow-up #1000 filed for the AGENTS.md trigger-words gap (P2 from same Greptile pass; AGENTS.md owned by another agent in this cohort).
@MScottAdams MScottAdams force-pushed the agent4/docs/979-984-readme-refinement-webinstaller branch from 102df15 to 3277c97 Compare May 8, 2026 22:46
@MScottAdams MScottAdams merged commit a3e1da5 into master May 8, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant