I disagree, I think it is a fair argument here. Sure, "full stack" as a pure definition would probably only mean at least one part display layer, one part backend layer... but in a framework sense, it's fair to include all these other important capabilities (translation, background jobs, etc.).