Dogfooding postmortem — 12 issues from two real-world deployments

[djdarcy]

Dogfooding postmortem — 12 issues found across two real-world deployments

Summary

Two back-to-back ghtraf deployments were documented in detail as dogfooding postmortems. The deployments covered:

1. djdarcy/ComfyUI-Smart-Resolution-Calc — first deployment, solo ComfyUI node project
2. DazzleNodes/DazzleNodes — second deployment (~30 min later), multi-node collection with org-level secrets

Together they surfaced 12 issues ranging from CLI UX gaps to missing template files. The second deployment confirmed that 3 of the issues are systematic bugs (not environmental flukes), and also demonstrated a ~40% time reduction when applying lessons from the first deployment.

Issues documented

#	Issue	Severity	Confirmed on both?
1	--dry-run doesn't imply --non-interactive — hangs waiting for input	Medium	—
2	--ci-workflows substitutes name but leaves workflow_run block commented	High	Yes
3	.nojekyll not included in dashboard templates	Medium	Yes
4	Step 4/5 prints PAT setup guidance even when org secret exists	Low	Yes
5	No --repo-dir auto-detection for create (only init auto-detects)	Low	—
6	Docs show ghtraf init before ghtraf create but don't explain sequencing	Low	—
7	--ci-workflows accepts filename but workflow_run expects name: field	Medium	—
8	GitHub Pages enablement not automated or clearly prompted	Low	—
9	External CI/registry clones not detected as non-organic	Informational	—
10	ghtraf create is not idempotent — creates duplicate gists on re-run	Medium	—
11	--ci-workflows help text doesn't clarify name: vs filename	Low	—
12	--configure in-place modification behavior not documented	Low	—

Where to find the postmortems

These are local project documentation files, not published online:

• Primary postmortem: 2026-03-01__23-01-56__full-postmortem_ghtraf-dogfood-setup.md in the djdarcy/ComfyUI-Smart-Resolution-Calc project — covers the first deployment end-to-end plus an addendum comparing both deployments
• DazzleNodes postmortem: 2026-03-02__00-22-58__full-postmortem_dazzlenodes-cascade-ghtraf.md in the DazzleNodes/DazzleNodes project — covers the second deployment as part of a broader cascade release

Why this matters

The postmortems were written with the ghtraf team in mind. They include:

• Exact CLI commands run (successes and failures)
• Step-by-step reproduction for each issue
• Suggested fixes with specific code locations
• A comparison table showing first vs second deployment efficiency
• Lessons-learned section identifying which manual workarounds could be eliminated

Suggested prioritization

Based on user impact during real deployments:

1. Issue 2 (workflow_run stays commented) — highest friction, requires manual YAML editing every deployment
2. Issue 10 (non-idempotent gist creation) — risk of orphaned gists, no recovery path
3. Issue 3 (.nojekyll missing) — GitHub Pages silently breaks without it
4. Issue 1 (dry-run hangs) — blocks the natural "preview before commit" workflow

Related issues

• Refs ghtraf — PyPI-distributed CLI tool for managing traffic tracking #6 — ghtraf CLI tool (parent tracking issue)
• Refs ghtraf init — copy workflow and dashboard templates into target repo #28 — ghtraf init template copy (Issue 3 relates to template completeness)
• Refs Wire ghtraf create --init to chain template copy + cloud setup #29 — ghtraf create --init chaining
• Refs ghtraf init --update — template merge/diff for upgrades #36 — ghtraf init --update for template upgrades