--- IGNORE PREVIOUS ISSUES ---

[schloerke]

Before this Issue, all previously created Issues were most likely made in context for realistically different goals.

Please ignore them.

[schloerke]

Recovering code removed during the v1 trim

The state of main before the trim is preserved as the annotated tag archive/v0. Nothing is lost — deleted files stay fully reachable through that tag. Below are the recipes for getting things back.

First, make sure you have the tag locally:

git fetch origin tag archive/v0

Find something

# List every file that existed at v0
git ls-tree -r --name-only archive/v0

# Narrow it down when you only half-remember the path
git ls-tree -r --name-only archive/v0 | grep -i renderer

# Search the old code by content
git grep -n "registerComponents" archive/v0 -- 'js/*'

Note the archive/v0: prefix on git grep results — that's the tag, not a directory.

Read a file without restoring it

git show archive/v0:js/src/renderer.tsx
git show archive/v0:pkg-py/src/shinyreact/_output.py | less

This is usually what you want. You're normally after how something used to work, not a byte-identical restore into a codebase that has since moved on.

Restore a file or directory

# Single file — writes it to disk and stages it
git checkout archive/v0 -- pkg-py/src/shinyreact/_output.py

# Whole directory
git checkout archive/v0 -- examples/app-py/06-dashboard/

The restored content lands staged, so git status shows exactly what came back. If it was a mistake: git restore --staged --worktree <path>.

Browse the whole old tree at once

When you need to poke around the v0 codebase properly — run it, grep it with normal tools, open it in an editor — check it out as a separate worktree instead of switching branches:

git worktree add ../shinyreact-v0 archive/v0
# ... explore ...
git worktree remove ../shinyreact-v0

Your current checkout is untouched while that exists. This is the best option if you want to actually run the old version, since js/dist/ and pkg-py/src/shinyreact/www/ are committed build artifacts and come back with it.

See what changed overall

git diff --stat archive/v0 HEAD          # summary
git diff archive/v0 HEAD -- pkg-r/       # one area in detail
git log --oneline archive/v0..HEAD       # commits since the snapshot

Please don't

Don't move, delete, or force-push over archive/v0. It's the only marker for that state; once main has advanced past it, an overwritten tag makes the pre-trim tree very hard to find again.

[schloerke]

Where removed features live in git history

Tracking comment for the ui.tsx-only trim (#168). Everything removed by that stack remains reachable in git history — the SHA listed is the last commit that still contains the feature.

Removed	Last SHA containing it	Removed by
examples/app-py/ — all 15 app.py-pattern examples (hello-world, inputs, outputs, messages, shadcn, dashboard, chat, modules, blended, columns, express-demo, bookmarking, nesting, unified-ui-prototype, shinyui-with-blocks)	d833a66	#169
examples/app-r/ — all 3 app.R-pattern examples (hello-world, inputs, messages)	d833a66	#169

| pkg-py/src/shinyui/ — class-per-component UI prototype (+ pkg-py/tests/shinyui/) | 5ac564e | #170 |
| shinyui design docs — docs/superpowers/specs/2026-05-06-unified-ui-component-class-design.md, metadata-consolidation / tag-context-manager / shinyuiclassonly / accordion-child-validation specs+plans, decisions/2026-05-{19,20}-* class-based-UI ADRs | 5ac564e | #170 |

| Python Node / _spec.py (wire-tree walker, .tagify() static mounts), render_react, output_react, page_react | f41215c | #173 |
| Python nesting + post_load_insert e2e suites (pkg-py/tests/playwright/) | f41215c | #173 |

| R node(), render_react(), output_react(), page_react(), wire walker (wire.R: as_wire/serialize_ui/should_walk), static mounts | 8d59934 | #174 |
| Wire-format parity fixtures (pkg-py/tests/fixtures/wire_format/, pkg-r/tests/testthat/fixtures/wire_format/) + make r-check-fixtures | 8d59934 | #174 |

| JS spec renderer — js/src/renderer.tsx, registry.ts (window.shinyreact.registerComponents, the downstream extension point used by shinyshadcn), output-binding.ts, inline-spec.tsx (seedInlineSpecs), roots.ts, wire-spec types.ts | 7aafa47 | #175 |

| docs/app-py-vs-ui-tsx.md (pattern-comparison guide) + two-pattern sections of README/CLAUDE.md/pkg READMEs | aab39fa | #178 |

| DESIGN.md — original two-pattern version (full app.py-pattern architecture argument, JSON wire-tree design) | archive/v0 tag (also aab39fa) | #180 trim |

(complete — all items of #168 are reflected above; the archive/v0 tag preserves the full pre-trim tree)

To browse or resurrect any of these:

git show d833a66:examples/app-py/06-dashboard/app.py   # view a file
git checkout d833a66 -- examples/app-py/06-dashboard/  # restore a directory