feat(presets): support regex selectors for command declarations by lmtyy · Pull Request #4776 · github/spec-kit

lmtyy · 2026-09-28T17:01:18Z

Closes #4659.

This replaces the previous (much larger) version of this PR with the focused change the
maintainer asked for: regex:<pattern> support for preset command declarations only.
Everything else that had accumulated here is split out into subsequent targeted PRs; the
full earlier work is preserved on the branch feat/4659-regex-preset-selectors-full
(2aa5e892) as the source for those follow-ups.

What this does

A preset may use a bounded selector in a provides.templates entry of type command:

provides:
  templates:
    - type: command
      name: 'regex:^speckit\\.(plan|tasks|implement)$'
      file: commands/workflow-guidance.md
      strategy: append

The selector is expanded, in declaration order, into the concrete lower-layer commands it
matches. Those concrete names then flow through the existing command resolution,
registration, composition and removal paths.
Matching is against the full logical command name only — never a path, file name or
substring — and only against commands that actually exist in the layers below (enabled
presets, enabled extensions, core, including built-in core). The declaring preset itself,
higher-priority presets and project-local overrides are not used as evidence of existence.
A literal selector string is never used as an output path, a .composed file name or a
registry key: the registry only ever sees concrete names.
A regex: name on a non-command declaration is a validation error, not a silent
no-op.
Entries without the prefix keep exact-name matching and are completely unaffected.
Diagnostics: preset info reports the commands a selector currently matches;
preset resolve <name> names the declaration that matched when a layer came from a
selector.
Matching is deterministic (declaration order preserved, overlapping declarations are not
de-duplicated away) and uses the bounded matcher with its existing limits.

Scope: what is deliberately not here

Split into follow-up PRs, each based on its own point in upstream/main:

template and script selectors, and selector support on the extension side;
automatic reconciliation after provider/integration changes (see the known limitation);
historical recovery sweeps and the ownership/ledger redesign beyond the minimal guard;
the install-transaction rework, snapshot/journal machinery and CLI boundary refactors
(design/cli.md, design/shared.md).

Kept deliberately, because the feature materializes command/skill files:

the minimal ownership-based guard on the command/skill write paths, so that a preset
install cannot overwrite artifacts the user has edited. This is a prerequisite for the
feature being safe, not a re-introduction of the wider ownership work.

Known limitations (please review with these in mind)

No automatic broadcast on provider change. A selector is expanded at install/enable
time and the existing reconciliation of concrete names still runs, but there is no new
mechanism that re-expands selectors when a new provider/integration appears. This is the
main user-visible limitation of the reduced scope and the reason the change is small.
Bounded regex subset. The matcher intentionally implements a bounded subset rather
than full Python regex compatibility; the limits and the rejection behaviour are covered
by tests.

Tests / evidence

Selector surface: tests/specify_cli/presets/test_regex_selectors.py,
test_selector_safety.py, test_selector_resolution_contract.py,
test_resolver_candidates.py, test_regex_selector_diagnostics.py — 146 passed.
Whole preset suite: 854 passed.
uvx ruff@0.15.0 check src tests: All checks passed; compileall clean;
git diff --check clean.
No tests were skipped, weakened or marked expected-failure to reach these numbers.
Against the same base, tests/specify_cli/test_file_policy.py shows the same 10
pre-existing failures / 177 passed before and after this change (verified on a pristine
checkout of the base) — i.e. this PR adds none.
Merged against the current main (which has moved past this branch's base) the full suite
is 12423 passed / 98 skipped / 0 failed — the change merges cleanly with the latest
base and does not regress it.
CI note: the workflow runs for a fork PR are in action_required state, i.e. they need a
maintainer to approve them before they execute. No CI result should be assumed for this
revision yet.
WINDOWS-VERIFIED: NO — the fork's Windows CI cannot be triggered from here, so the
Windows job must be treated as unverified for this revision. The earlier branch's Windows
fixes are not part of this PR (they belong with the files this PR does not touch).

AI disclosure

Authored with AI assistance (Hermes Agent); reviewed and verified against the test suite by
a human before submission.

Copilot

Copilot review overview

🟡 Changes recommended

Command resolution, skill registration, diagnostics, warnings, and lifecycle reconciliation have unresolved functional gaps.

Review effort: Balanced
Findings: 3 · 2

Open (5)

Include command selectors in layer resolution · New
Collect all matching regex declarations · New
Fix invalid specify_cli._selectors import · New
Expand selectors before AI skill registration · New
Reconcile selectors after preset and extension changes · New

What changed in this PR

Adds regex: resource selectors to preset resolution and command materialization.

Changes:

Validates and full-matches regex selectors.
Expands command selectors and adds lifecycle reconciliation.
Adds resolver and selector coverage.

File	Description
`tests/specify_cli/presets/test_regex_selectors.py`	Tests selector matching and resolution.
`src/specify_cli/presets/command_set_priority.py`	Reconciles commands after priority changes.
`src/specify_cli/presets/command_info.py`	Displays selector matches.
`src/specify_cli/presets/command_enable.py`	Reconciles enabled preset commands.
`src/specify_cli/presets/_selectors.py`	Implements selector helpers.
`src/specify_cli/presets/_resolver.py`	Resolves regex template and script layers.
`src/specify_cli/presets/_manifest.py`	Validates regex expressions.
`src/specify_cli/presets/_manager.py`	Integrates expansion into lifecycle handling.
`src/specify_cli/presets/_manager_commands.py`	Expands command selectors.

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

mnriem · 2026-09-28T17:28:29Z

Please address Copilot feedback

lmtyy · 2026-09-28T18:49:03Z

Addressed all five Copilot review findings:

Added command regex selectors to normal layer resolution and composition.
Preserved all matching regex declarations in manifest order.
Fixed the invalid _selectors imports used by diagnostics.
Reused selector expansion for AI-skill registration.
Added selector-aware reconciliation for relevant preset/extension lifecycle changes.

Also added regression coverage for overlapping selectors, command composition strategies, diagnostics, AI-skill registration, and lifecycle state changes.

Validation:

8624 passed, 17 skipped
183 targeted regression tests passed
Ruff passed
Python compilation passed
git diff --check passed

Copilot

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

lmtyy · 2026-09-29T02:44:05Z

All previous Copilot review findings have been addressed and the updated test suite is passing. The latest Copilot re-review appears to have failed due to a review error, so the PR is ready for another review when convenient.

Copilot

Copilot review overview

🟡 Changes recommended

Selector lifecycle paths can leave stale commands or skills and several acceptance criteria remain incomplete.

Review effort: Balanced
Findings: 6

Open (6)

Installation lacks warnings for unmatched resource selectors · New
Regex constitution selectors skip snapshot reconciliation · New
Regex command selectors are dropped during skill reconciliation · New
Extension manifest resources are omitted from diagnostics · New
Priority changes can persist despite failed reconciliation · New
Disabling presets leaves stale command and skill artifacts · New

mnriem · 2026-09-29T11:15:31Z

Please address Copilot feedback

Copilot

Copilot review overview

🟡 Changes recommended

Selector lifecycle transitions can leave stale or untracked command and skill artifacts.

Review effort: Balanced
Findings: 3 · 2

Open (5)

Cleanup ignores expanded selector declarations · New
Regex-owned commands bypass preset registration tracking · New
Regex-composed commands bypass preset ownership tracking · New
Preserve Templates count in preset info output · New
Add end-to-end lifecycle tests for selector artifacts · New

Resolved since last review (6)

Disabling presets leaves stale command and skill artifacts
Priority changes can persist despite failed reconciliation
Extension manifest resources are omitted from diagnostics
Regex command selectors are dropped during skill reconciliation
Regex constitution selectors skip snapshot reconciliation
Installation lacks warnings for unmatched resource selectors

Previously missed (1)

In code that hasn't changed since last review

Stale artifacts remain when selectors lose all matches

src/specify_cli/extensions/_commands.py:121

This refresh runs only after the extension state has changed, so a selector whose sole lower layer was disabled or removed now expands to nothing. register_enabled_presets_for_agent() never sees the previously materialized concrete name, and its reconciler also skips names with no remaining layers, leaving the old command/SKILL artifact active. Capture the pre-mutation matches (or persisted registrations), reconcile the union with post-mutation matches, and explicitly unregister names that no longer resolve.

Copilot

Copilot review overview

🟡 Changes recommended

Selector cleanup, disabled-extension resolution, and installation rollback still have correctness gaps.

Review effort: Balanced
Findings: 1 · 3

Open (4)

Fallback re-enables disabled extensions · New
Disabled presets ignored incorrectly by include_disabled · New
Removed selector matches leave stale registry entries · New
Disabling provider leaves orphaned command artifacts · New

Resolved since last review (5)

Regex-composed commands bypass preset ownership tracking
Regex-owned commands bypass preset registration tracking
Cleanup ignores expanded selector declarations
Add end-to-end lifecycle tests for selector artifacts
Preserve Templates count in preset info output

Previously missed (2)

In code that hasn't changed since last review

Selector expansion failure leaves partial installation

src/specify_cli/presets/_manager.py:456

Selector diagnostics and expansion run after the preset directory and registry entry are created but before the existing rollback guard. _expand_command_selectors() deliberately raises when artifact enumeration fails, so such a failure leaves an enabled, partially installed preset behind. Move both calls into the guarded installation phase so the established cleanup executes.

Re-enumeration causes false failure after registration

src/specify_cli/presets/_manager.py:507

This repeats artifact enumeration outside the transactional registration block. If inventory changes or becomes unreadable after registration, the command reports installation failure even though the preset and artifacts are already committed. Reuse the concrete command_templates computed for registration.

mnriem · 2026-09-29T16:30:13Z

Please address Copilot feedback

lmtyy · 2026-09-30T12:24:21Z

@mnriem I've addressed the latest Copilot feedback in commit 1ce59c1, including the disabled-extension fallback, include_disabled handling, stale selector tracking/cleanup, and install rollback coverage.

When convenient, could you please re-request the Copilot review? Thanks!

Copilot

Copilot review overview

🟡 Changes recommended

Selector rollback, disabled-state handling, and extension-layer deduplication contain unresolved correctness issues.

Review effort: Balanced
Findings: 1 · 5

Open (6)

Avoid recreating artifacts for disabled extensions · New
Check ownership when including disabled presets · New
Restore artifacts for regex-only preset rollback · New
Avoid duplicate extension command registration · New
Reconcile constitution after cleanup failure · New
Disabling provider leaves orphaned command artifacts

Resolved since last review (3)

Fallback re-enables disabled extensions
Removed selector matches leave stale registry entries
Disabled presets ignored incorrectly by include_disabled

Copilot

Copilot review overview

🟡 Changes recommended

Selector diagnostics, fallback resolution, and rollback paths still contain correctness gaps.

Review effort: Balanced
Findings: 2 · 8

Open (10)

Track outputs incrementally during registration · New
Avoid recreating artifacts for disabled extensions
Scope alternate-name fallback to the matching namespace · New
Include bundled resources in template and script diagnostics · New
Guard priority persistence and post-change selector scanning · New
Reconcile constitution after cleanup failure
Avoid duplicate extension command registration
Restore artifacts for regex-only preset rollback
Check ownership when including disabled presets
Disabling provider leaves orphaned command artifacts

mnriem · 2026-10-06T19:14:38Z

Please address Copilot feedback and resolve conflicts

lmtyy · 2026-10-07T16:32:21Z

@mnriem Thanks for your patience. I’ve addressed the latest Copilot feedback, resolved the upstream merge conflict, and pushed the updated changes.

The full test suite is passing locally, and the branch should now be ready for another review.

Thanks again for your time!

Copilot

🟡 Changes recommended

Extension disable, enable rollback, and reprioritization failure paths can leave artifacts or registry state inconsistent.

6 open findings

Make agent cleanup transactional to prevent partial disablement · New
Snapshot conventional command paths for complete rollback · New
Fail priority changes when preset reconciliation fails · New
Add regression test for extension priority recomposition
Update docs for preset disable artifact removal behavior
Document regex manifest syntax and expansion behavior

1 resolved since last review

Reconcile selector-generated outputs after extension removal

🧠 Review effort: Balanced

mnriem · 2026-10-07T19:08:03Z

Please address Copilot feedback and resolve conflicts

Copilot

🟡 Changes recommended

Selector lifecycle and transaction paths can leave missing, stale, or untracked artifacts in several failure and convention-only cases.

4 open findings

Refresh selectors for convention-only command candidates during installation · New
Reconcile selectors before committing extension disablement · New
Include disabled presets in legacy-root migration guards · New
Retain incrementally recorded outputs during command registration · New

6 resolved since last review

Make agent cleanup transactional to prevent partial disablement
Fail priority changes when preset reconciliation fails
Snapshot conventional command paths for complete rollback
Add regression test for extension priority recomposition
Update docs for preset disable artifact removal behavior
Document regex manifest syntax and expansion behavior

🧠 Review effort: Balanced

Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.

+        # Command/skill winners were materialized atomically by the installer;
+        # a best-effort second pass would publish the same concrete outputs again.


mnriem · 2026-10-08T12:17:04Z

Please address Copilot feedback and fix test & lint errors

Copilot

🔵 Needs a closer look

Resolution diagnostics still omit the selector attribution required by the linked acceptance criteria.

1 open finding

Refresh selectors for convention-only command candidates during installation

3 resolved since last review

Retain incrementally recorded outputs during command registration
Include disabled presets in legacy-root migration guards
Reconcile selectors before committing extension disablement

Previously missed (1)

In code that hasn't changed since last review

Preserve selector attribution in preset resolve diagnostics

src/specify_cli/presets/command_info.py:170

The linked acceptance criteria also require resolution diagnostics to show which selector matched each concrete resource, but this expansion is only rendered by preset info. preset resolve still receives layers containing only the preset source/path/strategy, so its composition chain cannot distinguish a regex match from an exact declaration or display the selector expression. Please carry selector attribution into resolved layers and render it in the resolution diagnostic as well.

🧠 Review effort: Balanced

Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.

mnriem · 2026-10-08T16:25:27Z

Please address Copilot feedback

Copilot

🟡 Changes recommended

Legacy refresh paths can leave stale selector artifacts, and unrestricted backtracking regexes can hang CLI operations.

3 open findings

Prevent catastrophic regex backtracking from hanging the CLI · New
Reconcile stale preset outputs when init-options.json is missing · New
Refresh selectors for convention-only command candidates during installation

🧠 Review effort: Balanced

mnriem · 2026-10-09T14:56:50Z

Please address Copilot feedback and fix test & lint errors

Copilot

🟡 Changes recommended

Extension disable can leave skill-only artifacts active under a previously selected integration.

3 open findings

2 resolved since last review

🧠 Review effort: Balanced

mnriem · 2026-10-12T19:28:29Z

Please address Copilot feedback and address test & lint errors

Copilot

🟡 Changes recommended

Conventional lower-preset commands remain unresolved, rollback can mask the original error, and lifecycle orchestration violates the documented CLI boundary.

9 open findings

2 resolved since last review

🧠 Review effort: Balanced

+        for directory in sorted(
+            (item for item in root.rglob("*") if item.is_dir() and not item.is_symlink()),
+            key=lambda item: len(item.parts),
+            reverse=True,
+        ):


+        # ``templates/commands`` is a conventional command location in its own
+        # right: _conventional_command_names and _expand_command_selectors both
+        # enumerate it, for lower presets as well as for extensions. Searching it
+        # here — at the single shared lookup — is what keeps the preset-side
+        # eligibility check that calls this method directly in agreement with
+        # selector expansion; otherwise a matched resource is never offered as a
+        # layer and the selector materializes nothing.
+        subdirs = {
+            "template": ("templates", ""),
+            "command": ("commands", "templates/commands"),


+        # Cleanup mutates several agents' artifacts, both registries, and the
+        # hook config, and it changes which lower layer preset selectors can
+        # match. A failure part-way through must not leave the extension
+        # enabled with the earlier agents already stripped, nor disabled with
+        # artifacts still composed from its layer, so snapshot every touched
+        # destination first, reconcile selectors strictly inside the same
+        # transaction, and restore everything as a unit on error.
+        import copy

-    # Disable hooks in extensions.yml
-    config = hook_executor.get_project_config()
-    if "hooks" in config:
-        for hook_name in config["hooks"]:
-            for hook in config["hooks"][hook_name]:
-                if hook.get("extension") == extension_id:
-                    hook["enabled"] = False
-        hook_executor.save_project_config(config)
-
-    console.print(f"[green]✓[/green] Extension '{_escape_markup(str(display_name))}' disabled")
+        from ..presets import PresetManager
+        from ..presets._transaction import _ArtifactSnapshot, _capture_preset_artifacts


+        # Enabling makes lower layers visible to selectors. Snapshot before
+        # publishing eligibility, including ownership of every refreshed winner.
+        import copy
+
+        from ..presets import PresetManager
+        from ..presets._transaction import _ArtifactSnapshot, _capture_preset_artifacts


+    # Extension reordering can change the lower-layer candidates matched by
+    # enabled preset regex selectors, so the new priority is only committed
+    # together with the recomposed artifacts. Mirrors the preset priority
+    # transaction: snapshot the artifact trees and both registries, run the
+    # reconciliation strictly, and roll back to the previous priority on any
+    # failure instead of reporting a change that never reached the
+    # selector-backed outputs.
+    import copy
+
+    from ..presets import PresetManager
+    from ..presets._transaction import _ArtifactSnapshot, _capture_preset_artifacts


+    from ._resolver import PresetResolver
+
+    resolver = PresetResolver(project_root)
+    affected = manager._collect_selector_command_names(resolver)
+    manifest = resolver._get_manifest(manager.presets_dir / preset_id)


+    # Capture selector matches while the preset is disabled, then enable it and
+    # reconcile the newly active resolution stack.
+    from ._resolver import PresetResolver
+
+    resolver = PresetResolver(project_root)


+    registry_before = copy.deepcopy(manager.registry.data)
+    snapshot = _ArtifactSnapshot()
+    captured = False
+    try:
+        # Capture before even the first scan: directory resolution may create
+        # skill roots, and rollback must not depend on the failing resolver.
+        _capture_preset_artifacts(manager, snapshot)


mnriem · 2026-10-13T18:11:09Z

I am so sorry to ask for this and thank you for being so diligent in addressing the feedback. To keep the change focused and reviewable, can we please limit this PR to supporting regex:<pattern> for preset command declarations only, then address the remaining areas in subsequent targeted PRs? I am afraid we won't land this as it has snowballed and diverged from the original intent

A preset may declare `regex:<pattern>` in a `provides.templates` entry of type `command`. At install/enable time the selector expands, in declaration order, into the concrete lower-layer commands it matches; those names then flow through the existing command resolution, registration, tracking and removal behaviour. Matching is against the full logical command name only, never a path, file name or substring, and a literal selector is never used as an output path, composed file name or registry key. Non-command declarations using a selector are rejected during validation. Diagnostics: `preset info` reports the commands a selector currently matches and `preset resolve <name>` attributes selector-contributed layers. Kept from the earlier work: the self-contained selector engine, the bounded matching limits with their tests, the minimal ownership-based guard on the command/skill materialization write paths, and the command-only docs. Deliberately out of scope, for subsequent targeted PRs: template/script selectors, extension-side selectors, automatic reconciliation after provider changes, historical recovery sweeps, and the install-transaction rework. AI disclosure: this change was authored with AI assistance (Hermes Agent); all behaviour was reviewed and verified against the test suite by a human.

lmtyy · 2026-10-14T06:04:50Z

Hi — thank you for the guidance, and sorry for letting this PR grow well past the original intent (it had reached 69 files).

I have now replaced it with a focused version: regex: support for preset command declarations only, expanding into concrete command names that then flow through the existing resolution and registration paths, with selectors rejected on non-command declarations. It is a single commit and 15 files (+3,446/−115). The remaining areas — template/script selectors, extension-side selectors, reconciliation after provider changes, and the lifecycle/transaction work — will come as separate targeted PRs, each based on its own point in main.

Locally the full suite is green on this revision (12,410 passed, 0 failed), and it also stays green after merging the current main (12,423 passed, 0 failed). The workflow runs are currently action_required, so there is no CI result yet — I would appreciate it if you could approve them.

Could you take another look when you have a chance?

lmtyy requested a review from mnriem as a code owner September 28, 2026 17:01

mnriem requested a balanced review from Copilot September 28, 2026 17:21

Copilot started reviewing on behalf of mnriem September 28, 2026 17:23 View session

Copilot AI reviewed Sep 28, 2026

View reviewed changes

mnriem requested a balanced review from Copilot September 28, 2026 19:28

Copilot started reviewing on behalf of mnriem September 28, 2026 19:30 View session

Copilot AI reviewed Sep 28, 2026

mnriem added the triage-can-wait Verdict: valid and in-scope but deprioritized; held behind the evidence gate label Sep 28, 2026

mnriem requested a balanced review from Copilot September 29, 2026 10:52

Copilot started reviewing on behalf of mnriem September 29, 2026 10:53 View session

Copilot AI reviewed Sep 29, 2026

View reviewed changes

mnriem requested a balanced review from Copilot September 29, 2026 13:49

Copilot started reviewing on behalf of mnriem September 29, 2026 13:49 View session

Copilot AI reviewed Sep 29, 2026

View reviewed changes

mnriem requested a balanced review from Copilot September 29, 2026 16:16

Copilot started reviewing on behalf of mnriem September 29, 2026 16:17 View session

Copilot AI reviewed Sep 29, 2026

View reviewed changes

Comment thread src/specify_cli/presets/_resolver.py Outdated

Comment thread src/specify_cli/integrations/_command_upgrade_layout.py Outdated

Comment thread src/specify_cli/presets/_manager_commands.py

Comment thread src/specify_cli/presets/command_disable.py Outdated

mnriem requested a balanced review from Copilot September 30, 2026 13:34

Copilot started reviewing on behalf of mnriem September 30, 2026 13:35 View session

Copilot AI reviewed Sep 30, 2026

View reviewed changes

mnriem requested a balanced review from Copilot September 30, 2026 14:50

Copilot started reviewing on behalf of mnriem September 30, 2026 14:51 View session

Copilot AI reviewed Sep 30, 2026

View reviewed changes

Comment thread src/specify_cli/extensions/__init__.py Outdated

Comment thread src/specify_cli/presets/_resolver.py Outdated

Comment thread src/specify_cli/presets/command_info.py Outdated

Comment thread src/specify_cli/presets/command_set_priority.py Outdated

mnriem requested a balanced review from Copilot September 30, 2026 16:52

mnriem requested a balanced review from Copilot October 7, 2026 19:01

Copilot started reviewing on behalf of mnriem October 7, 2026 19:02 View session

Copilot AI reviewed Oct 7, 2026

View reviewed changes

Comment thread src/specify_cli/extensions/command_disable.py Outdated

Comment thread src/specify_cli/extensions/command_enable.py Outdated

Comment thread src/specify_cli/extensions/command_set_priority.py Outdated

mnriem requested a balanced review from Copilot October 8, 2026 11:45

Copilot started reviewing on behalf of mnriem October 8, 2026 11:45 View session

Copilot AI reviewed Oct 8, 2026

View reviewed changes

mnriem requested a balanced review from Copilot October 8, 2026 16:10

Copilot started reviewing on behalf of mnriem October 8, 2026 16:11 View session

Copilot AI reviewed Oct 8, 2026

View reviewed changes

mnriem requested a balanced review from Copilot October 9, 2026 13:35

Copilot started reviewing on behalf of mnriem October 9, 2026 13:36 View session

Copilot AI reviewed Oct 9, 2026

View reviewed changes

Comment thread src/specify_cli/presets/_selectors.py Outdated

Comment thread src/specify_cli/extensions/_commands.py Outdated

mnriem requested a balanced review from Copilot October 12, 2026 14:06

Copilot started reviewing on behalf of mnriem October 12, 2026 14:07 View session

Copilot AI reviewed Oct 12, 2026

View reviewed changes

Comment thread src/specify_cli/extensions/command_disable.py Outdated

Comment thread src/specify_cli/presets/_selectors.py Outdated

mnriem requested a balanced review from Copilot October 13, 2026 17:43

Copilot started reviewing on behalf of mnriem October 13, 2026 17:44 View session

Copilot AI reviewed Oct 13, 2026

View reviewed changes

lmtyy force-pushed the feat/4659-regex-preset-selectors branch from 234c727 to 647c7c8 Compare October 14, 2026 04:34

lmtyy changed the title ~~feat(presets): support regex resource selectors~~ feat(presets): support regex selectors for command declarations Oct 14, 2026

		# Command/skill winners were materialized atomically by the installer;
		# a best-effort second pass would publish the same concrete outputs again.

Conversation

lmtyy commented Sep 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What this does

Scope: what is deliberately not here

Known limitations (please review with these in mind)

Tests / evidence

AI disclosure

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot review overview

🟡 Changes recommended

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

mnriem commented Sep 28, 2026

Uh oh!

lmtyy commented Sep 28, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

lmtyy commented Sep 29, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot review overview

🟡 Changes recommended

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

mnriem commented Sep 29, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot review overview

🟡 Changes recommended

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot review overview

🟡 Changes recommended

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

mnriem commented Sep 29, 2026

Uh oh!

lmtyy commented Sep 30, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot review overview

🟡 Changes recommended

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot review overview

🟡 Changes recommended

Uh oh!

Uh oh!

lmtyy commented Sep 28, 2026 •

edited

Loading