get-tbd 0.1.13 → 0.1.14

package/dist/docs/guidelines/typescript-yaml-handling-rules.md

@@ -0,0 +1,195 @@
+---
+title: TypeScript YAML Handling Rules
+description: Best practices for parsing and serializing YAML in TypeScript
+author: Joshua Levy (github.com/jlevy) with LLM assistance
+globs: "*.ts"
+---
+# TypeScript YAML Handling Rules
+
+These guidelines ensure consistent, safe, and readable YAML handling across TypeScript
+codebases. YAML is deceptively tricky—inconsistent quoting, serialization differences,
+and lack of validation cause subtle bugs.
+
+## Use the Right Package
+
+- **Use `yaml` (v2.x)**, not `js-yaml`. The `yaml` package has better TypeScript
+  support, more control over output formatting, and proper handling of edge cases.
+
+  ```ts
+  // Good
+  import { parse, stringify } from 'yaml';
+  
+  // Avoid
+  import yaml from 'js-yaml';
+  ```
+
+## Centralize Serialization Options
+
+- **Externalize settings to a central file** instead of scattering `stringify()` calls
+  with ad-hoc options throughout the codebase.
+
+  ```ts
+  // lib/settings.ts
+  export const DEFAULT_YAML_LINE_WIDTH = 88;
+  
+  // Readable YAML output:
+  // - No forced quoting (YAML only quotes when necessary)
+  // - Line wrapping at 88 chars for readability
+  // - Sorted keys for deterministic diffs
+  export const YAML_STRINGIFY_OPTIONS = {
+    lineWidth: DEFAULT_YAML_LINE_WIDTH,
+    defaultStringType: 'PLAIN',
+    defaultKeyType: 'PLAIN',
+    sortMapEntries: true,
+  } as const;
+  ```
+
+- **Use the centralized options** wherever you serialize YAML:
+
+  ```ts
+  // serialize.ts
+  import { stringify } from 'yaml';
+  import { YAML_STRINGIFY_OPTIONS } from '../lib/settings.js';
+  
+  const yamlStr = stringify(frontmatterObj, YAML_STRINGIFY_OPTIONS);
+  ```
+
+- **Optionally create wrapper functions** for additional convenience:
+
+  ```ts
+  // utils/yaml-utils.ts
+  import { stringify } from 'yaml';
+  import { YAML_STRINGIFY_OPTIONS } from '../lib/settings.js';
+  
+  export function stringifyYaml(data: unknown, options?: object): string {
+    return stringify(data, { ...YAML_STRINGIFY_OPTIONS, ...options });
+  }
+  ```
+
+## Recommended Defaults
+
+These defaults produce clean, readable YAML without unnecessary quoting:
+
+| Option | Value | Rationale |
+| --- | --- | --- |
+| `lineWidth` | 88 | Line wrapping for readability (matches Black formatter) |
+| `defaultStringType` | `'PLAIN'` | No quotes unless necessary (e.g., special chars, colons) |
+| `defaultKeyType` | `'PLAIN'` | Unquoted keys: `name:` not `"name":` |
+| `sortMapEntries` | `true` | Deterministic output for clean diffs |
+
+The key insight: YAML is designed to be human-readable.
+Forcing quotes everywhere (e.g., `"value"` instead of `value`) defeats this purpose.
+Use `PLAIN` types to let YAML quote only when semantically required.
+
+## Validate with Zod
+
+- **Always validate parsed YAML** with a Zod schema.
+  Raw `parse()` returns `unknown` and provides no guarantees about structure.
+
+  ```ts
+  // Good
+  import { z } from 'zod';
+  import { parse } from 'yaml';
+  
+  const ConfigSchema = z.object({
+    name: z.string(),
+    version: z.string(),
+  });
+  
+  const rawData = parse(content);
+  const result = ConfigSchema.safeParse(rawData);
+  if (!result.success) {
+    throw new Error(`Invalid config: ${result.error.message}`);
+  }
+  const config = result.data; // Typed and validated
+  
+  // Avoid
+  const config = parse(content) as Config; // Type assertion with no runtime validation
+  ```
+
+## Handle Merge Conflicts
+
+- **Check for git merge conflict markers** before parsing user-editable files.
+  Conflict markers cause cryptic YAML parse errors.
+
+  ```ts
+  export function parseYamlWithConflictDetection<T>(content: string, filePath?: string): T {
+    if (/^<<<<<<< /m.test(content) || /^=======/m.test(content) || /^>>>>>>> /m.test(content)) {
+      throw new MergeConflictError(
+        `File contains unresolved git merge conflict markers`,
+        filePath
+      );
+    }
+    return parse(content) as T;
+  }
+  ```
+
+## Common Antipatterns
+
+### Antipattern: Manual String Building
+
+```ts
+// Bad: Manual YAML string construction
+const yaml = `name: ${name}\nversion: ${version}`;
+
+// Good: Use stringify()
+const yaml = stringifyYaml({ name, version });
+```
+
+### Antipattern: Inconsistent Quoting
+
+```ts
+// Bad: Inconsistent options across codebase
+stringify(data1, { lineWidth: 80 });
+stringify(data2, { lineWidth: 100, defaultStringType: 'QUOTE_DOUBLE' });
+stringify(data3); // No options
+
+// Good: Use centralized wrapper
+stringifyYaml(data1);
+stringifyYaml(data2);
+stringifyYaml(data3);
+```
+
+### Antipattern: Unvalidated Parsing
+
+```ts
+// Bad: Type assertion without validation
+const config = parse(content) as Config;
+
+// Good: Runtime validation
+const config = ConfigSchema.parse(parse(content));
+```
+
+### Antipattern: Using gray-matter Directly for Serialization
+
+```ts
+// Bad: gray-matter.stringify() has limited formatting control
+import matter from 'gray-matter';
+const output = matter.stringify(body, frontmatter);
+
+// Good: Use gray-matter for parsing, yaml package for serialization
+import matter from 'gray-matter';
+import { stringifyYaml } from './yaml-utils.js';
+
+const { data, content } = matter(input);
+const output = `---\n${stringifyYaml(data)}---\n\n${content}`;
+```
+
+## Testing YAML Output
+
+- **Don’t rely on key order in tests** when using `sortMapEntries: true`. Keys are
+  sorted alphabetically.
+
+  ```ts
+  // Fragile: Depends on key order
+  expect(yaml).toMatch(/^---\nname: foo\nversion: 1/);
+  
+  // Robust: Tests presence, not order
+  expect(yaml).toContain('name: foo');
+  expect(yaml).toContain('version: 1');
+  ```
+
+## Related Guidelines
+
+- For general TypeScript rules, see `tbd guidelines typescript-rules`
+- For error handling patterns, see `tbd guidelines error-handling-rules`

package/dist/docs/install/claude-header.md

@@ -1,12 +1,19 @@
 ---
 name: tbd
 description: >-
-  Git-native issue tracking (beads), coding guidelines, and spec-driven planning for AI agents.
-  Use for tracking issues with dependencies, creating and closing bugs, features, and tasks,
-  planning specs for new features, implementing features from specs, code reviews, committing code,
-  creating PRs, research briefs, and architecture docs. Invoke when user mentions: tbd, beads,
-  issues, bugs, tasks, todo, tracking, specs, planning, implementation, validation, guidelines,
-  shortcuts, templates, commit, PR workflows, code review, testing best practices, or monorepo patterns.
+  Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven
+  planning for AI agents. Drop-in replacement for bd/Beads with simpler architecture.
+
+  Use for: tracking issues/beads with dependencies, creating bugs/features/tasks, planning specs,
+  implementing features from specs, code reviews, committing code, creating PRs, loading coding
+  guidelines (TypeScript, Python, TDD, golden testing, Convex, monorepo patterns), code cleanup,
+  research briefs, architecture docs, agent handoffs, and checking out third-party library source code.
+
+  Invoke when user mentions: tbd, beads, bd, shortcuts, issues, bugs, tasks, features, epics, todo,
+  tracking, specs, planning, implementation, validation, guidelines, templates, commit, PR, pull request,
+  code review, testing, TDD, test-driven, golden testing, snapshot testing, TypeScript, Python, Convex,
+  monorepo, cleanup, dead code, refactor, handoff, research, architecture, labels, search, checkout library,
+  source code review, or any workflow shortcut.
 allowed-tools: Bash(tbd:*), Read, Write
 ---
 

package/dist/docs/shortcuts/standard/agent-handoff.md

@@ -1,6 +1,7 @@
 ---
 title: Agent Handoff
 description: Generate a concise handoff prompt for another coding agent to continue work
+category: session
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 Generate a high-signal handoff prompt for the next agent.

package/dist/docs/shortcuts/standard/checkout-third-party-repo.md

@@ -0,0 +1,50 @@
+---
+title: Checkout Third-Party Repo
+description: Get source code for libraries and third-party repos using git. Essential for reliable source code review. Prefer this to web searches or fetching of web pages from github.com as it is far more effective (github.com blocks web scraping from main website).
+category: research
+author: Joshua Levy (github.com/jlevy) with LLM assistance
+---
+Clone a third-party library or tool’s repository locally to review its source code.
+
+## Why This Approach
+
+**Do not** use web search or try to scrape GitHub.com for source code.
+GitHub blocks scraping, results are messy, and you lose full codebase context.
+Cloning locally gives you reliable, complete, searchable access to the exact version you
+need.
+
+## Steps
+
+1. **Create attic directory** (if not exists):
+   ```bash
+   mkdir -p attic
+   ```
+
+2. **Add to .gitignore** (if not already):
+   ```bash
+   echo "attic/" >> .gitignore
+   ```
+
+3. **Identify the version in use**: Check `package.json`, `requirements.txt`,
+   `Cargo.toml`, etc. for the exact version of the dependency you’re investigating.
+
+4. **Clone the repo**:
+   ```bash
+   git clone <repo-url> attic/<repo-name>
+   ```
+
+5. **Checkout the matching version**: Find the tag or branch matching your project’s
+   version:
+   ```bash
+   cd attic/<repo-name>
+   git tag -l | grep <version>   # Find matching tag
+   git checkout <tag-or-branch>
+   ```
+
+6. **Explore**: Now use standard tools (Grep, Read, Glob) to investigate the source.
+
+## Notes
+
+- The `attic/` directory is gitignored—cloned repos won’t pollute your project
+- You can clone multiple repos into attic/ as needed
+- Delete cloned repos when done to save disk space

package/dist/docs/shortcuts/standard/{cleanup-all.md → code-cleanup-all.md}

@@ -1,6 +1,7 @@
 ---
 title: Clean Up All Code
 description: Full cleanup cycle including duplicate removal, dead code, and code quality improvements
+category: cleanup
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 # Shortcut: Clean Up Code
@@ -52,9 +53,9 @@ cycle afterwords, fixing all build or test issues.
    - Review types and eliminate use of optional types as possible so we don’t spread
      state checks throughout the codebase.
 
-7. **Remove trivial tests**: Follow `tbd shortcut cleanup-remove-trivial-tests`.
+7. **Remove trivial tests**: Follow `tbd shortcut code-cleanup-tests`.
 
-8. **Update docstrings**: Follow `tbd shortcut cleanup-update-docstrings`.
+8. **Update docstrings**: Follow `tbd shortcut code-cleanup-docstrings`.
 
 9. **Consolidate constants and settings**: Determine what files hold shared settings
    (such as `settings.ts` or similar).

package/dist/docs/shortcuts/standard/{cleanup-update-docstrings.md → code-cleanup-docstrings.md}

@@ -1,6 +1,7 @@
 ---
 title: "Cleanup: Update Docstrings"
 description: Review and add concise docstrings to major functions and types
+category: cleanup
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 # Shortcut: Update Docstrings

package/dist/docs/shortcuts/standard/{cleanup-remove-trivial-tests.md → code-cleanup-tests.md}

@@ -1,6 +1,7 @@
 ---
 title: "Cleanup: Remove Trivial Tests"
 description: Review and remove tests that do not add meaningful coverage
+category: cleanup
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 # Shortcut: Remove Trivial Tests

package/dist/docs/shortcuts/standard/{commit-code.md → code-review-and-commit.md}

@@ -1,6 +1,7 @@
 ---
 title: Commit Code
 description: Run pre-commit checks, review changes, and commit code
+category: git
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 We track work as beads using tbd.

package/dist/docs/shortcuts/standard/create-or-update-pr-simple.md

@@ -1,6 +1,7 @@
 ---
 title: Create or Update PR (Simple)
 description: Create or update a pull request with a concise summary
+category: git
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 We track work as beads using tbd.

package/dist/docs/shortcuts/standard/create-or-update-pr-with-validation-plan.md

@@ -1,6 +1,7 @@
 ---
 title: Create or Update PR with Validation Plan
 description: Create or update a pull request with a detailed test/validation plan
+category: git
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 We track work as beads using tbd.

package/dist/docs/shortcuts/standard/implement-beads.md

@@ -1,6 +1,7 @@
 ---
 title: Implement Beads
 description: Implement beads from a spec, following TDD and project rules
+category: planning
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 We track work as beads using tbd.

package/dist/docs/shortcuts/standard/merge-upstream.md

@@ -1,6 +1,7 @@
 ---
 title: Merge Upstream
 description: Merge origin/main into current branch with conflict resolution
+category: git
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 Merge upstream changes from origin/main into the current branch.

package/dist/docs/shortcuts/standard/new-architecture-doc.md

@@ -1,6 +1,7 @@
 ---
 title: New Architecture Doc
 description: Create an architecture document for a system or component design
+category: documentation
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 We track work as beads using tbd.

package/dist/docs/shortcuts/standard/new-guideline.md

@@ -1,6 +1,7 @@
 ---
 title: New Guideline
 description: Create a new coding guideline document for tbd
+category: meta
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 This shortcut helps create new guideline documents that agents can reference via
@@ -87,6 +88,11 @@ Create a to-do list with the following items then perform all of them:
    - Rebuild tbd: `pnpm build` (in packages/tbd/)
    - Verify bundled: check `packages/tbd/dist/docs/guidelines/<name>.md`
 
+9. **Update documentation** (for official guidelines):
+   - Add to root `README.md` “Built-in Engineering Knowledge” table
+   - Sync docs cache: `tbd setup --auto` (updates `.tbd/docs/`)
+   - Note: `packages/tbd/README.md` is auto-copied from root during build
+
 ## Guideline Quality Checklist
 
 - [ ] Frontmatter has title and description
@@ -96,6 +102,8 @@ Create a to-do list with the following items then perform all of them:
 - [ ] Cross-references to related guidelines
 - [ ] No relative links (use full URLs for external refs)
 - [ ] Tested with `tbd guidelines <name>`
+- [ ] (Official) Added to root README.md “Built-in Engineering Knowledge” table
+- [ ] (Official) Docs cache synced: `tbd setup --auto`
 
 ## Example Frontmatter
 

package/dist/docs/shortcuts/standard/new-plan-spec.md

@@ -1,6 +1,7 @@
 ---
 title: New Plan Spec
 description: Create a new feature planning specification document
+category: planning
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 We track work as beads using tbd.

package/dist/docs/shortcuts/standard/new-research-brief.md

@@ -1,6 +1,7 @@
 ---
 title: New Research Doc
 description: Create a research document for investigating a topic or technology
+category: documentation
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 We track work as beads using tbd.

package/dist/docs/shortcuts/standard/new-shortcut.md

@@ -1,6 +1,7 @@
 ---
 title: New Shortcut
 description: Create a new shortcut (reusable instruction template) for tbd
+category: meta
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 Create a new shortcut for `tbd shortcut <name>`.
@@ -16,6 +17,7 @@ Create a new shortcut for `tbd shortcut <name>`.
 ---
 title: [Title]
 description: [One line for --list output]
+category: [category]
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 [Concise instructions. Focus on what's specific to this task.
@@ -23,11 +25,26 @@ Skip obvious steps the agent would figure out.
 Reference other shortcuts/guidelines/templates as needed.]
 ```
 
+## Categories
+
+Use one of these standard categories in the frontmatter:
+
+| Category | Use For |
+| --- | --- |
+| `planning` | Spec creation, implementation planning, validation plans |
+| `documentation` | Research briefs, architecture docs, doc revisions |
+| `review` | Code review, PR review |
+| `git` | Commits, PRs, merging, pre-commit workflows |
+| `cleanup` | Code cleanup, dead code removal, test cleanup |
+| `session` | Session management, handoffs, setup, recovery |
+| `meta` | Creating new shortcuts/guidelines |
+| `research` | Research tasks, third-party code checkout |
+
 ## Naming
 
 Use kebab-case: `new-<thing>`, `<verb>-<noun>`, `<thing>-<variant>`
 
-Examples: `commit-code`, `new-plan-spec`, `review-code-typescript`
+Examples: `code-review-and-commit`, `new-plan-spec`, `review-code-typescript`
 
 ## Key Principles
 
@@ -45,6 +62,15 @@ tbd shortcut --list      # Verify listing
 
 For official shortcuts: `pnpm build` in packages/tbd/
 
+## Documentation Updates (Official Shortcuts)
+
+For official shortcuts added to `packages/tbd/docs/shortcuts/standard/`:
+
+1. **Update root README.md** — Add to the “Available shortcuts” table (grouped by
+   category: Planning, Documentation, Review, Git, Cleanup, Session, Meta)
+2. **Sync docs cache** — Run `tbd setup --auto` to update `.tbd/docs/`
+3. **Rebuild** — `pnpm build` in packages/tbd/ (also copies README to package)
+
 ## Shortcuts vs Guidelines
 
 - **Shortcuts**: Workflows to follow (process)

package/dist/docs/shortcuts/standard/new-validation-plan.md

@@ -1,6 +1,7 @@
 ---
 title: New Validation Plan
 description: Create a validation/test plan showing what's tested and what remains
+category: planning
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 Create a validation plan documenting completed and remaining validation work.

package/dist/docs/shortcuts/standard/plan-implementation-with-beads.md

@@ -1,6 +1,7 @@
 ---
 title: Plan Implementation with Beads
 description: Create implementation beads from a feature planning spec
+category: planning
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 Break a plan spec (or other work) into implementation beads.

package/dist/docs/shortcuts/standard/precommit-process.md

@@ -1,6 +1,7 @@
 ---
 title: Pre-Commit Process
 description: Full pre-commit checklist including spec sync, code review, and testing
+category: git
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 We track work as beads using tbd.

package/dist/docs/shortcuts/standard/review-code-python.md

@@ -1,6 +1,7 @@
 ---
 title: Review Code (Python)
 description: Python-focused code review (language-specific rules only)
+category: review
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 This shortcut performs a **Python-focused** code review, checking Python-specific best

package/dist/docs/shortcuts/standard/review-code-typescript.md

@@ -1,6 +1,7 @@
 ---
 title: Review Code (TypeScript)
 description: TypeScript-focused code review (language-specific rules only)
+category: review
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 This shortcut performs a **TypeScript-focused** code review, checking

package/dist/docs/shortcuts/standard/review-code.md

@@ -1,6 +1,7 @@
 ---
 title: Review Code
 description: Comprehensive code review for uncommitted changes, branch work, or GitHub PRs
+category: review
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 This is the **core code review** shortcut.

package/dist/docs/shortcuts/standard/review-github-pr.md

@@ -1,6 +1,7 @@
 ---
 title: Review GitHub PR
 description: Review a GitHub pull request with follow-up actions (comment, fix, CI check)
+category: review
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 This shortcut reviews a **GitHub pull request** and handles GitHub-specific follow-ups

package/dist/docs/shortcuts/standard/revise-all-architecture-docs.md

@@ -1,6 +1,7 @@
 ---
 title: Revise All Architecture Docs
 description: Comprehensive revision of all current architecture documents
+category: documentation
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 We track work as beads using tbd.

package/dist/docs/shortcuts/standard/revise-architecture-doc.md

@@ -1,6 +1,7 @@
 ---
 title: Revise Architecture Doc
 description: Update an architecture document to reflect current codebase state
+category: documentation
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 Review and update an architecture document to ensure accuracy with current code.

package/dist/docs/shortcuts/standard/setup-github-cli.md

@@ -1,6 +1,7 @@
 ---
 title: Setup GitHub CLI
 description: Ensure GitHub CLI (gh) is installed and working
+category: session
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 The GitHub CLI (`gh`) is required for PR and issue operations.

package/dist/docs/shortcuts/standard/sync-failure-recovery.md

@@ -1,16 +1,13 @@
 ---
 title: Sync Failure Recovery
 description: Handle tbd sync failures by saving to workspace and recovering later
+category: session
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 When `tbd sync` fails to push (e.g., network errors, permission issues, branch
 restrictions), use this workflow to preserve and recover issue data.
 
-## Workflow
-
-### 1. When sync fails
-
-If `tbd sync` fails with a push error:
+## When Sync Fails
 
 ```bash
 # Save unsynced changes to the outbox
@@ -22,9 +19,7 @@ git commit -m "tbd: save outbox"
 git push
 ```
 
-The `--outbox` flag saves only issues modified since the last successful sync.
-
-### 2. Later, when sync works
+## Later, When Sync Works
 
 In a new session or environment where sync works:
 
@@ -36,52 +31,10 @@ tbd import --outbox
 tbd sync
 ```
 
-## Understanding Workspaces
-
-Workspaces are directories under `.tbd/workspaces/` that store issue backups.
-
-- `tbd save --outbox` saves to `.tbd/workspaces/outbox/`
-- `tbd import --outbox` imports from outbox and clears it on success
-- Workspaces are committed to your working branch (not gitignored)
+## More Information
 
-## Alternative: Named Workspaces
-
-For backups or bulk editing, use named workspaces:
+For detailed troubleshooting, workspace usage, and diagnostic commands, see:
 
 ```bash
-# Create a backup
-tbd save --workspace=backup-2026-01
-
-# Save to arbitrary directory
-tbd save --dir=/tmp/issues-backup
-
-# Import from named workspace
-tbd import --workspace=backup-2026-01
+tbd guidelines sync-troubleshooting
 ```
-
-## Checking Workspace Status
-
-```bash
-# List all workspaces
-tbd workspace list
-
-# See workspaces in tbd status output
-tbd status
-```
-
-## Multi-Agent Scenarios
-
-Multiple agents can save to the same outbox:
-
-- Different issues: No conflicts, all preserved
-- Same issue edited compatibly: Merged automatically
-- Same issue with conflicts: Conflict goes to attic for review
-
-## Troubleshooting
-
-If sync continues to fail:
-
-1. Check network connectivity
-2. Verify push permissions: `git push --dry-run origin tbd-sync`
-3. Check for branch restrictions in your environment
-4. Review error message from `tbd sync` for specific guidance

package/dist/docs/shortcuts/standard/update-specs-status.md

@@ -1,6 +1,7 @@
 ---
 title: Update Specs Status
 description: Review active specs and sync their status with tbd issues
+category: planning
 author: Joshua Levy (github.com/jlevy) with LLM assistance
 ---
 Review all active specs and ensure tbd issues accurately reflect current progress.