Give a prop a start and stop lifecycle

local active = true
return function()
    if not active then return end
    active = false
    connection:Disconnect()
end

The first cleanup changes state and disconnects. The second cleanup returns immediately.

New syntax: lifecycle, cleanup, idempotency

• collectionservice
• tags

Module owns its event resource.

local InspectBehavior = {}
function InspectBehavior.attach(part)
    local prompt = part:FindFirstChildOfClass("ProximityPrompt")
    assert(prompt, "Add a ProximityPrompt")
    local active = true
    local connection = prompt.Triggered:Connect(function(player)
        if active then print("Inspect", part.Name, player.Name) end
    end)
    return function()
        if not active then return end
        active = false
        connection:Disconnect()
    end
end
return InspectBehavior

Controller releases resources when membership ends.

local CollectionService = game:GetService("CollectionService")
local Behavior = require(script.Parent.InspectBehavior)
local cleanups = {}
local function attach(part)
    if cleanups[part] or not part:IsA("BasePart") then return end
    cleanups[part] = Behavior.attach(part)
end
local function detach(part)
    if cleanups[part] then cleanups[part](); cleanups[part] = nil end
end
CollectionService:GetInstanceAddedSignal("WorkshopLamp"):Connect(attach)
CollectionService:GetInstanceRemovedSignal("WorkshopLamp"):Connect(detach)
for _, part in ipairs(CollectionService:GetTagged("WorkshopLamp")) do attach(part) end

If reattachment logs twice, the old connection was not released.

Calling Disconnect on the signal itself is different from disconnecting the returned connection.

This is a bounded learning lab. It has not been executed in an approved Roblox Studio environment by this website.

A checked checklist records your own review, not automated project competence or a community verification.

An attachment owns the resources it creates: connections, tweens, and temporary tables. Its cleanup function releases those resources.

Idempotent cleanup can be called twice safely. A simple active flag prevents repeated teardown and tells callbacks the attachment is finished.

The controller stores cleanup functions by object. Removing a tag and destroying an object are lifecycle events; leaving the client does not automatically express every behavior cleanup policy.