refactor: clean core experiment

[freelerobot]

This PR (originally an experiment) refactors types into clean entities

[louis-jan]

@0xSage, (abstract) classes are available at runtime, while interfaces are compile-time only. We built the core SDK to allow the Extension Builder and App to inherit/use it, mostly at runtime. There are a bunch of type checking to let app can poll correct extensions to invoke their function at runtime.

let x: any;
// IThreadExtension is an interface 
if (x instanceof IThreadExtension) { // Error: 'ThreadExtension' only refers to a type, but is being used as a value here.

}
// ThreadExtension is an abstract class
if (x instanceof ThreadExtension) { // OK

}

[freelerobot]

@0xSage, (abstract) classes are available at runtime, while interfaces are compile-time only. We built the core SDK to allow the Extension Builder and App to inherit/use it, mostly at runtime. There are a bunch of type checking to let app can poll correct extensions to invoke their function at runtime.

Yes, I realized this while refactoring Events (still in progress). Reverting the ai-kit extensions back to abstract classes.
Maybe ignore this PR for a few hours, it is very POC 😓

[dan-homebrew]

I'm really not sure ai-kit and node-kit are good names. Please reconsider

[freelerobot]

@louis-jan our codebase has evolved significantly since I did this experiment (kudos to you and team).

What pieces of this experiment should actually be merged in?

What about refactoring types and interfaces into something like:

/types
  /assistant
    assistant.ts (for types, enums, globals)
    assistantInterface.ts (for interface definition)
    index.ts (simply exports types & interfaces)

such that (s.t.):
/core/extensions can just be:
export abstract class AssistantExtension extends BaseExtension implements AssistantInterface.

It may seem redundant but it decouples interfaces from extensions (and makes dep path clearer).

For any changes worthy of being incorporated, I'd like @hieu-jan to take over from here.

[louis-jan]

@louis-jan our codebase has evolved significantly since I did this experiment (kudos to you and team).

What pieces of this experiment should actually be merged in?

What about refactoring types and interfaces into something like:

/types
  /assistant
    assistant.ts (for types, enums, globals)
    assistantInterface.ts (for interface definition)
    index.ts (simply exports types & interfaces)

such that (s.t.): /core/extensions can just be: export abstract class AssistantExtension extends BaseExtension implements AssistantInterface.

It may seem redundant but it decouples interfaces from extensions (and makes dep path clearer).

For any changes worthy of being incorporated, I'd like @hieu-jan to take over from here.

@0xSage The types refactoring is neat. Please merge, also decouples interfaces, totally agree.

[freelerobot]

Closing this PR in favor of #966